Method and apparatus for restricting ue session management procedure retry after network rejection

ABSTRACT

A method of operating a user equipment (UE) in a wireless communications network includes sending, from the UE to a first network element, a first packet service session management request message indicating a request of a first session management service type for at least one of establishing a new packet data session or modifying an existing packet data session, the first packet service session management request message being sent towards a first access point name (APN); receiving, at the UE, a rejection message, the rejection message indicating the request of the first session management service type has been rejected; and performing a retry operation after receiving the rejection message, the retry operation including sending, from the UE, a second packet service session management request message of the first session management service type towards the first APN, the retry operation being prevented by the UE such that the retry operation is not performed by the UE until after at least one of, an expiration of a retry timer of the UE, or detection, at the UE, of a retry trigger event.

CROSS-REFERENCE TO RELATED APPLICATIONS

This non-provisional application claims the benefit of priority under 35U.S.C. §119(e) to U.S. Provisional Application No. 61/919,951, filed onDec. 23, 2013, and U.S. Provisional Application No. 62/070,119, filed onAug. 15, 2014 the entire contents of each of which are incorporatedherein by reference.

BACKGROUND

1. Field

This invention relates generally to mobile communication systems, andmore specifically to a manner of controlling UE (user equipment) sessionmanagement messages in an attempt to reduce or eliminate inefficienttraffic.

2. Related Art

In a 3GPP packet data network, UE retry signaling results from rejectionof evolved packet system (EPS) session management (ESM)/sessionmanagement (SM) procedures. These ESM/SM procedures can be PDNCONNECTIVITY REQUEST, BEARER RESOURCE ALLOCATION REQUEST, BEARERRESOURCE MODIFICATION REQUEST, ACTIVATE PDP CONTEXT REQUEST, ACTIVATESECONDARY PDP CONTEXT REQUEST and MODIFY PDP CONTEXT REQUEST. Once thoseESM or SM messages are rejected e.g. with cause value #32 (serviceoption not supported), #33 (requested service option not subscribed), #8(operator determined barring), #27 (missing or unknown APN), #97(message type non-existent or not implemented), etc., a UE mayre-attempt the failed ESM/SM procedures.

SUMMARY

According to one or more example embodiments, a method of operating auser equipment (UE) in a wireless communications network may includesending, from the UE to a first network element, a first packet servicesession management request message indicating a request of a firstsession management service type for at least one of establishing a newpacket data session or modifying an existing packet data session, thefirst packet service session management request message being sent for afirst access point name (APN); receiving, at the UE, a rejectionmessage, the rejection message indicating the request of the firstsession management service type has been rejected; and performing aretry operation after receiving the rejection message, the retryoperation including sending, from the UE, a second packet servicesession management request message of the first session managementservice type towards the first APN, the retry operation being preventedby the UE such that the retry operation is not performed by the UE untilafter at least one of, an expiration of a retry timer of the UE, ordetection, at the UE, of a retry trigger event.

According to one or more example embodiments, a user equipment (UE) mayinclude a processing unit including a processor, the UE being programmedto perform, with the processor, operations including, sending, from theUE to a first network element, a first packet service session managementrequest message indicating a request of a first session managementservice type for at least one of establishing a new packet data sessionor modifying an existing packet data session, the first packet servicesession management request message being sent towards a first accesspoint name (APN); receiving, at the UE, a rejection message, therejection message indicating the request for of the first sessionmanagement service type has been rejected; and performing a retryoperation after receiving the rejection message, the retry operationincluding sending, from the UE, a second packet service sessionmanagement request message of the first session management service typetowards the first APN, the retry operation being prevented by the UEsuch that the retry operation is not performed by the UE until after atleast one of, an expiration of a retry timer of the UE, or detection, atthe UE, of a retry trigger event.

BRIEF DESCRIPTION OF THE DRAWINGS

At least some example embodiments will become more fully understood fromthe detailed description provided below and the accompanying drawings,wherein like elements are represented by like reference numerals, whichare given by way of illustration only and thus are not limiting ofexample embodiments and wherein:

FIG. 1 is a diagram illustrating a portion of a wireless communicationsnetwork according to at least one example embodiment.

FIG. 2A is a diagram illustrating an example structure of a userequipment (UE) according to at least one example embodiment.

FIG. 2B is a diagram illustrating an example structure of a networkelement according to at least one example embodiment.

FIG. 3A illustrates a 4G evolved packet core (EPC) network example ofproviding UE retry restriction using an ESM reject message without aretry wait time according to at least one example embodiment.

FIG. 3B illustrates a 4G EPC network example of providing UE retryrestriction using an ESM reject message with a retry wait time accordingto at least one example embodiment.

FIG. 4A illustrates a 4G EPC network example of providing UE retryrestriction using an ESM status message without a retry wait timeaccording to at least one example embodiment.

FIG. 4B illustrates a 4G EPC network example of providing UE retryrestriction using an ESM status message with a retry wait time accordingto at least one example embodiment.

FIG. 5 is a flow chart illustrating an example of logic executed by a UEwhen handling a PDN CONNECTIVITY REJECT message in accordance with oneor more example embodiments.

FIG. 6 is a flow chart illustrating an example of logic executed by a UEwhen handling a BEARER RESOURCE ALLOCATION REJECT message in accordancewith one or more example embodiments.

FIG. 7 is a flow chart illustrating an example of logic executed by a UEwhen handling a BEARER RESOURCE MODIFICATION REJECT message inaccordance with one or more example embodiments.

FIG. 8 is a flow chart illustrating an example of logic executed by a UEwhen handling a ESM STATUS message in accordance with one or moreexample embodiments.

FIG. 9 illustrates a general packet radio service (GPRS) network exampleof providing UE retry restriction using an ESM reject message without aretry wait time according to at least one example embodiment.

FIG. 10 illustrates a GPRS network example of providing UE retryrestriction using an ESM reject message with a retry wait time accordingto at least one example embodiment.

FIG. 11 illustrates a GPRS network example of providing UE retryrestriction using an ESM status message without a retry wait timeaccording to at least one example embodiment.

FIG. 12 illustrates a GPRS network example of providing UE retryrestriction using an ESM status message with a retry wait time accordingto at least one example embodiment.

FIG. 13 is a flow chart illustrating an example of logic executed by aUE when handling an ACTIVATE PDP CONTEXT REJECT message in accordancewith one or more example embodiments.

FIG. 14 is a flow chart illustrating an example of logic executed by aUE when handling an ACTIVATE SECONDARY PDP CONTEXT REJECT message inaccordance with one or more example embodiments.

FIG. 15 is a flow chart illustrating an example of logic executed by aUE when handling a MODIFY PDP CONTEXT REJECT message in accordance withone or more example embodiments.

FIG. 16 is a flow chart illustrating an example of logic executed by aUE when handling a SM STATUS message in accordance with one or moreexample embodiments.

FIG. 17 illustrates a 4G EPC network example of providing UE retryrestriction using an RAT dependency indicator indicating an RATindependent mode and a retry wait time in an ESM reject message.

FIG. 18 illustrates a 4G EPC network example of providing UE retryrestriction using an RAT dependency indicator indicating an RATdependent mode without a retry wait time in an ESM reject message.

FIG. 19 illustrates a 4G EPC network example of providing UE retryrestriction using a RAT dependency indicator indicating an RATindependent mode and a retry wait time value in an ESM reject message.

FIG. 20 illustrates a 4G EPC network example of providing UE retryrestriction using a RAT dependency indicator indicating an RATindependent mode and no retry wait time value in an ESM reject message.

FIGS. 21A and 21B illustrate 4G EPC network examples of providing UEretry restriction using the absence or presence of a retry wait timevalue in an ESM reject message as a RAT dependency indicator indicatingan RAT independent mode.

FIG. 22 illustrates a GPRS network example of providing UE retryrestriction using an RAT dependency indicator indicating an RATindependent mode and a retry wait time in an SM reject message.

FIG. 23 illustrates a GPRS network example of providing UE retryrestriction using an RAT dependency indicator indicating an RATdependent mode without a retry wait time in an SM reject message.

FIG. 24 illustrates a GPRS network example of providing UE retryrestriction using a RAT dependency indicator indicating an RATindependent mode and a retry wait time value in an SM reject message.

FIG. 25 illustrates a GPRS network example of providing UE retryrestriction using a RAT dependency indicator indicating an RATindependent mode and no retry wait time value in an SM reject message.

FIGS. 26A and 26B illustrate GPRS network examples of providing UE retryrestriction using the absence or presence of a retry wait time value inan SM reject message as a RAT dependency indicator indicating an RATindependent mode.

DETAILED DESCRIPTION OF EXAMPLE EMBODIMENTS

Various example embodiments will now be described more fully withreference to the accompanying drawings in which some example embodimentsare shown.

Detailed illustrative embodiments are disclosed herein. However,specific structural and functional details disclosed herein are merelyrepresentative for purposes of describing at least some exampleembodiments. Example embodiments may, however, be embodied in manyalternate forms and should not be construed as limited to only theembodiments set forth herein.

Accordingly, while example embodiments are capable of variousmodifications and alternative forms, embodiments thereof are shown byway of example in the drawings and will herein be described in detail.It should be understood, however, that there is no intent to limitexample embodiments to the particular forms disclosed, but on thecontrary, example embodiments are to cover all modifications,equivalents, and alternatives falling within the scope of exampleembodiments. Like numbers refer to like elements throughout thedescription of the figures. As used herein, the term “and/or” includesany and all combinations of one or more of the associated listed items.

It will be understood that when an element is referred to as being“connected” or “coupled” to another element, it can be directlyconnected or coupled to the other element or intervening elements may bepresent. In contrast, when an element is referred to as being “directlyconnected” or “directly coupled” to another element, there are nointervening elements present. Other words used to describe therelationship between elements should be interpreted in a like fashion(e.g., “between” versus “directly between”, “adjacent” versus “directlyadjacent”, etc.).

The terminology used herein is for the purpose of describing particularembodiments only and is not intended to be limiting of exampleembodiments. As used herein, the singular forms “a”, “an” and “the” areintended to include the plural forms as well, unless the context clearlyindicates otherwise. It will be further understood that the terms“comprises”, “comprising,”, “includes” and/or “including”, when usedherein, specify the presence of stated features, integers, steps,operations, elements, and/or components, but do not preclude thepresence or addition of one or more other features, integers, steps,operations, elements, components, and/or groups thereof.

It should also be noted that in some alternative implementations, thefunctions/acts noted may occur out of the order noted in the figures.For example, two figures shown in succession may in fact be executedsubstantially concurrently or may sometimes be executed in the reverseorder, depending upon the functionality/acts involved.

As used herein, the term user equipment (UE) may be consideredsynonymous to, and may hereafter be occasionally referred to, as aterminal, mobile unit, mobile device, mobile station, mobile user,access terminal (AT), subscriber, user, remote station, access terminal,receiver, etc., and may describe a remote user of wireless resources ina wireless communication network. The term evolved Node B (eNB) may beconsidered synonymous to and/or referred to as a base transceiverstation (BTS), base station (BS), Home eNB (HeNB), access point (AP),etc. and may describe equipment that provides the radio basebandfunctions for data and/or voice connectivity between a network and oneor more users, for example, in a long term evolution (LTE) network. Theterm Node B may be considered synonymous to and/or referred to as a basetransceiver station (BTS), base station (BS), access point (AP), etc.and may describe equipment that provides the radio baseband functionsfor data and/or voice connectivity between a network and one or moreusers, for example, in a general packet radio service (GPRS) network.

Exemplary embodiments are discussed herein as being implemented in asuitable computing environment. Although not required, exemplaryembodiments will be described in the general context ofcomputer-executable instructions, such as program modules or functionalprocesses, being executed by one or more computer processors or CPUs.Generally, program modules or functional processes include routines,programs, objects, components, data structures, etc. that performsparticular tasks or implement particular abstract data types.

The program modules and functional processes discussed herein may beimplemented using existing hardware in existing communication networks.For example, program modules and functional processes discussed hereinmay be implemented using existing hardware at existing network elementsor control nodes (e.g., a serving general packet radio service (GPRS)support node (SGSN) or mobility management entity (MME) shown in FIG.1). Such existing hardware may include one or more digital signalprocessors (DSPs), application-specific-integrated-circuits (ASICs),field programmable gate arrays (FPGAs) computers or the like.

In the following description, illustrative embodiments will be describedwith reference to acts and symbolic representations of operations (e.g.,in the form of flowcharts) that are performed by one or more processors,unless indicated otherwise. As such, it will be understood that suchacts and operations, which are at times referred to as beingcomputer-executed, include the manipulation by the processor ofelectrical signals representing data in a structured form. Thismanipulation transforms the data or maintains it at locations in thememory system of the computer, which reconfigures or otherwise altersthe operation of the computer in a manner well understood by thoseskilled in the art.

As is discussed above, when evolved packet system (EPS) sessionmanagement (ESM) messages or session management (SM) messages arerejected with, for example, any 3GPP specific session management causevalue including, for example, #32, #33, #8, #27 or #97 (as defined, forexample, by 3GPP TS24.008 V12.7.0 (2014-09), the entire contents ofwhich is incorporated herein, by reference), a UE may perform retryoperations. The UE may perform the retry operations aggressively, whichresults in a significant amount of additional signaling. This additionalsignaling consumes network resources needlessly and is thus undesirable.

As used herein, the term retry operation refers to an operation in whicha UE attempts to send, to a network element, a message, including forexample an ESM or SM request message, that was previously rejected by anetwork element, examples of which include an MME or SGSN.

For example, in some networks, approximately 80% of Create-PDP-Requestmessages may be a result of phones stuck in infinite loops sendingCreate-PDP-Request and getting Reject Cause #33: requested serviceoption not subscribed back from the network.

Accordingly, it is desirable from network resource efficiency usagepoint of view to restrict UE retry in these rejection scenarios. Forthese cause values, retrying the same request for the same access pointname (APN) under the same radio access technology (RAT) and public landmobile network (PLMN) combination may not be effective. If the MME haspreviously already rejected the same session management request from theUE and if other processing conditions (like APN, RAT, PLMN) have notbeen changed, or the UE has not changed subscription (which requires apower cycle), repeating the same SM requests that had previously beenrejected will be virtually guaranteed to receive the same rejectionagain. To prevent a network from being overloaded with unnecessary retryrequests, retry restriction may be applied so that the UE does notinitiate the same request unless some change in processing conditionscould potentially lead to processing result other than anotherrejection.

One possible solution of the problem described above would be tointroduce retry restriction on the UE so that when the UE is rejected,the UE will not automatically retry the session management request thatwas previously sent by the UE for the same APN until certain retryconditions have been met.

A problem with this approach, however, is that the session managementrequest may be restricted for very long time if the UE is static (notmoving to new PLMN or new RAT or new cells). In this case, since the UEwill not retry the session management request, there will be no eventpegging in operator's network. Then, it is almost impossible for anoperator to determine what the problem really is. Depending on operatornetwork, some operators may wish to take some network actions to resolvethe issue, for example, e.g. by modifying network node behavior,correcting a configuration mismatch, or shutting the UEs down if that isthe better solution. For these operators, it would be helpful to let theUE continue to retry at a reasonable rate of signaling.

In one embodiment, a solution is proposed to allow the flexibility forthe operator to detect session management issues and, at the same time,to prevent an abundance network signaling in a case where UE sessionmanagement requests are rejected by the network due to a rejectionscause including, for example, “service option not supported”, “requestedservice option not subscribed” or “message type non-existent or notimplemented”. According to one or more example embodiments, a new mobilesession management retry handling is introduced for at least theabove-referenced rejection cases so that the UE's unnecessary andabundant retry signaling is restricted both by a set of retry triggeringcriteria and by a configurable retry wait timer that is signaled to UEby the network during rejection. For example, according to one or moreexample embodiments, the UE will not automatically retry a sessionmanagement request that was previously sent by the UE for the same APNuntil certain retry conditions have been met

Consequently, the UE is not prevented from retrying rejected ESM or SMmessages in all cases, but the UE is restricted such that the retryattempts are made in a meaningful way by preventing useless retries(i.e., retries that have a high probability of failure due to lack ofchange in the circumstances that caused the previous failure).Accordingly, network overload caused by copious unnecessary retryrequests is prevented while the operator is still able to monitor therejection situation if desired. As will be discussed in greater detailbelow with reference to FIGS. 4-30, in accordance with one or moreexample embodiments, the UE is allowed to retry as soon as there is achange of condition (referred as “retry triggering criteria”) that couldpotentially yield different processing result, or if operatordependent/pre-configured “retry wait time” has elapsed.

The term “retry”/“retires”/“retried”, as used herein with reference to aUE (e.g., the UE retries . . . ), refers to the UE trying to send an ESMor SM message (or perform an ESM/SM procedure) of a particular sessionmanagement service type for a particular APN again after receiving arejection message in response to a previous attempt to send an ESM or SMmessage (or perform an ESM/SM procedure) of the same session managementservice type for the same APN. As used herein, sending a message “for”an APN refers to sending the message towards the APN.

Further, for the purpose of simplicity, five example ESM/SM causevalues, #32, #33, #8, #27 and #97, are referenced herein. However,according to one or more example embodiments, the operations describedherein with reference to cause values #32, #33 #8, #27 and #97 may applyto any 3GPP specific session management cause value. For example,according to one or more example embodiments, operations describedherein as being performed in response to receiving an ESM/SM rejectionmessage or ESM/SM status message including ESM/SM cause value #32, #33,#8, #27 or #97 may be performed in response to receiving an ESM/SMrejection or status message including any 3GPP specific sessionmanagement cause value. According to one other example embodiment,operations described herein as being performed in response to receivingan ESM/SM rejection message or ESM/SM status message including ESM/SMcause value #32, #33, #8, #27 or #97 may be performed in response toreceiving an ESM/SM rejection or status message including any of asubset, but not all, of the 3GPP specific session management causevalues, where the subset of values is chosen in accordance with thepreferences of the network operator.

Overview of Network Architecture

FIG. 1 is a diagram illustrating a portion of a wireless communicationsnetwork 100. Referring to FIG. 1, according to one or more exampleembodiments, the wireless communications network 100 may include twodifferent networks following two different wireless communicationsprotocols. For example, as is illustrated in FIG. 1, the wirelesscommunications network 100 may include a first network following thegeneral packet radio service (GPRS) protocol, GPRS network 110, and asecond network following the long term evolution (LTE) protocol, LTEnetwork 150. A user equipment (UE) 105 may be attached to at least oneof the GPRS network 110 and the LTE network 150.

The GPRS network 110 may include a serving general packet radio service(GPRS) support node (SGSN) 120, a radio network controller RNC 130, anda NodeB 140. The SGSN 120 is connected to the RNC 130. Though only oneRNC is illustrated, the SGSN 120 may be connected to multiple RNCs. TheSGSN 120 may handle operations including routing of data packets to RNCsconnected to the SGSN 120.

The RNC 130 is connected to the NodeB 140. Though only one Node B isillustrated in FIG. 1, the RNC 130 may be connected to multiple NodeBs.The RNC 130 may perform operations including controlling Node Bsconnected to the RNC 130.

The NodeB may provide UEs within a range of the NodeB 140 with wirelessaccess to the GPRS network 110 such that the UEs can send data to, andreceive data from, the GPRS network 110.

The GPRS network 100 may also include additional GPRS core networkcomponents not shown in FIG. 1.

The LTE network 150 includes a mobility management entity (MME) 160 andan evolved NodeB (eNB) 170.

The MME 160 is connected to the eNB 170. Though only one eNB 170 isillustrated in FIG. 1, the MME 160 may be connected to multiple eNBs.Further, the eNB 170 may provide UEs within a range of the eNB 170 withwireless access to the LTE network 150 such that the UEs can send datato, and receive data from the LTE network 150. The MME 160 may handleoperations including managing the movement of UEs throughout differentareas covered by the LTE network 150.

Example Network Element and UE Structures

FIG. 2A is a diagram illustrating an example structure of a UE 201.According to example embodiments, any or all UEs in the communicationsnetwork 100 may have the same structure and operation as UE 201described below.

The UE 201 may include, for example, a UE transmitting unit 210, a UEreceiving unit 220, a memory unit 230, a processing unit 240, and a databus 250.

The UE transmitting unit 210, UE receiving unit 220, memory unit 230,and processing unit 240 may send data to and/or receive data from oneanother using the data bus 250. The UE transmitting unit 210 is a devicethat includes hardware and any necessary software for transmittingwireless signals on an uplink (reverse link) channel including, forexample, data signals or control signals, via one or more wirelessconnections to other wireless devices (e.g., eNBs, other UEs, etc.).

The UE receiving unit 220 is a device that includes hardware and anynecessary software for receiving wireless signals on a downlink (forwardlink) channel including, for example, data signals or control signals,via one or more wireless connections to other wireless devices (e.g.,eNBs, other UEs, etc.).

The memory unit 230 may be any storage medium capable of storing dataincluding magnetic storage, flash storage, etc.

The processing unit 240 may be any device capable of processing dataincluding, for example, a processor. The term ‘processor’, as usedherein, refers to, for example, a hardware-implemented data processingdevice having circuitry that is physically structured to execute desiredoperations including, for example, operations represented as code and/orinstructions included in a program. Examples of the above-referencedhardware-implemented data processing device include, but are not limitedto, a microprocessor, a central processing unit (CPU), a processor core,a multiprocessor, an application-specific integrated circuit (ASIC), anda field programmable gate array (FPGA).

According to at least one example embodiment, any operations describedherein, for example with reference to any of FIGS. 1-26B, as beingperformed by a UE may be performed by an electronic device having thestructure of the UE 201 illustrated in FIG. 2A. For example, accordingto at least one example embodiment, the UE 201 may be programmed, interms of software and/or hardware, to perform any or all of thefunctions described herein as being performed by a UE.

Consequently, each of the UEs described herein may be embodied asspecial purpose computers through software and/or hardware programming.

Examples of the UE 201 being programmed, in terms of software, toperform any or all of the functions described herein as being performedby any of the UEs described herein will now be discussed below. Forexample, the memory unit 230 may store a program including executableinstructions corresponding to any or all of the operations describedherein with reference to FIGS. 1-26B as being performed by a UE.According to at least one example embodiment, additionally oralternatively to being stored in the memory unit 230, the executableinstructions may be stored in a computer-readable medium including, forexample, an optical disc, flash drive, SD card, etc., and the UE 201 mayinclude hardware for reading data stored on the computerreadable-medium. Further, the processing unit 240 may be a processorconfigured to perform any or all of the operations described herein withreference to FIGS. 1-26B as being performed by a UE, for example, byreading and executing the executable instructions stored in at least oneof the memory unit 230 and a computer readable storage medium loadedinto hardware included in the UE 201 for reading computer-readablemediums.

Examples of the UE 201 being programmed, in terms of hardware, toperform any or all of the functions described herein as being performedby a UE will now be discussed below. Additionally or alternatively toexecutable instructions corresponding to the functions described withreference to FIGS. 1-26B as being performed by a network element beingstored in a memory unit or a computer-readable medium as is discussedabove, the processing unit 240 may include a circuit that has astructural design dedicated to performing any or all of the operationsdescribed herein with reference to FIGS. 1-26B as being performed by aUE. For example, the above-referenced circuit included in the processingunit 240 may be a FPGA or ASIC physically programmed, through specificcircuit design, to perform any or all of the operations described withreference to FIGS. 1-26B as being performed by a UE.

FIG. 2B is a diagram illustrating an example structure of a networkelement 251. According to example embodiments, any or all eNBs in thecommunications network 100, including for example the SGSN 120, RNC 130,NodeB 140, MME 160, and eNB 170, may have the structure and operationdescribed below with respect to network element 251.

Referring to FIG. 2B, the network element 251 may include, for example,a data bus 259, a transmitting unit 252, a receiving unit 254, a memoryunit 256, and a processing unit 258.

The transmitting unit 252, receiving unit 254, memory unit 256, andprocessing unit 258 may send data to and/or receive data from oneanother using the data bus 259.

The transmitting unit 252 is a device that includes hardware and anynecessary software for transmitting signals including, for example,control signals or data signals via one or more wired and/or wirelessconnections to one or more other network elements in communicationsnetwork 105. The transmitting unit may also transmit signals to UEs.

The receiving unit 254 is a device that includes hardware and anynecessary software for receiving wireless signals including, forexample, control signals or data signals via one or more wired and/orwireless connections to one or more other network elements in thecommunications network 100. The receiving unit may also receive signalsfrom UEs.

The memory unit 256 may be any device capable of storing data includingmagnetic storage, flash storage, etc.

The processing unit 258 may be any device capable of processing dataincluding, for example, a processor.

According to at least one example embodiment, any operations describedherein, for example with reference to any of FIGS. 1-26B, as beingperformed by a network element may be performed by an electronic devicehaving the structure of the network element 251 illustrated in FIG. 2B.Examples of network elements include a SGSN, RNC, NodeB, MME, or eNB.For example, according to at least one example embodiment, the networkelement 251 may be programmed, in terms of software and/or hardware, toperform any or all of the functions described herein as being performedby a network element. Consequently, each of the network elementsdescribed herein may be embodied as special purpose computers throughsoftware and/or hardware programming.

Examples of the network element 251 being programmed, in terms ofsoftware, to perform any or all of the functions described herein asbeing performed by any of the network elements described herein will nowbe discussed below. For example, the memory unit 256 may store a programincluding executable instructions corresponding to any or all of theoperations described herein with reference to FIGS. 1-26B as beingperformed by a network element. According to at least one exampleembodiment, additionally or alternatively to being stored in the memoryunit 256, the executable instructions may be stored in acomputer-readable medium including, for example, an optical disc, flashdrive, SD card, etc., and the network element 251 may include hardwarefor reading data stored on the computer readable-medium. Further, theprocessing unit 258 may be a processor configured to perform any or allof the operations described herein with reference to FIGS. 1-26B asbeing performed by a network element, for example, by reading andexecuting the executable instructions stored in at least one of thememory unit 256 and a computer readable storage medium loaded intohardware included in the network element 251 for readingcomputer-readable mediums.

Examples of the network element 251 being programmed, in terms ofhardware, to perform any or all of the functions described herein asbeing performed by a network element will now be discussed below.Additionally or alternatively to executable instructions correspondingto the functions described with reference to FIGS. 1-26B as beingperformed by a network element being stored in a memory unit or acomputer-readable medium as is discussed above, the processing unit 258may include a circuit that has a structural design dedicated toperforming any or all of the operations described herein with referenceto FIGS. 1-26B as being performed by a network element. For example, theabove-referenced circuit included in the processing unit 258 may be aFPGA or ASIC physically programmed, through specific circuit design, toperform any or all of the operations described with reference to FIGS.1-26B as being performed by a network element.

Providing UE Retry Restriction for 4G Evolved Packet Core (EPC) Network

One or more example embodiments of providing UE retry restriction for a4G EPC network will now be discussed below with reference to FIGS. 3A-8and communications network 100 in FIG. 1.

When session management requests (PDN CONNECTIVITY REQUEST, BEARERRESOURCE ALLOCATION REQUEST, BEARER RESOURCE MODIFICATION REQUEST)requested by a mobile (e.g., the UE 105) are rejected by the network(e.g., the LTE network 150), and a reject message is sent back with ESMcause #32 “service option not supported” or #33 “requested serviceoption not subscribed” or #8 (operator determined barring) or #27(missing or unknown APN) or #97 “message type non-existent or notimplemented”, an MME (e.g., the MME 160) can choose to simply restrictthe mobile retry based on a set of retry triggering criteria including,for example, the mobile selecting a new PLMN; the mobile moving to a newRAT; and the mobile switching off or the subscriber identity module(SIM)/universal SIM (USIM) being removed. According to one or moreexample embodiments, if any of the retry triggering conditions are met,the mobile can retry, as will be discussed in greater detail below withreference to FIG. 3A.

FIG. 3A illustrates a 4G EPC network example of providing UE retryrestriction using an ESM reject message without a retry wait time.

Referring to FIG. 3A, in step S305 the UE 105 may initiate an ESMrequest start timer T348x and send an ESM request message to the MME160. The ESM request message may have a message type value of, forexample, PDN CONNECTIVITY REQUEST, BEARER RESOURCE ALLOCATION REQUEST,or BEARER RESOURCE MODIFICATION REQUEST.

In step S310, the MME 160 may send an ESM reject message to the UE 105.The ESM reject message may have a message type value of, for example,PDN CONNECTIVITY REJECT, BEARER RESOURCE ALLOCATION REJECT, or BEARERRESOURCE MODIFICATION REJECT. The ESM reject message may have an ESMcause value of, for example, “service option not supported”, “requestedservice option not subscribed”, or “message type non-existent or notimplemented”. The ESM reject message sent in step S310 may not include aretry wait time value.

In step S315, the UE 105 stops timer T348x. According to one or moreexample embodiments, the UE 105 will not attempt a retry operation untila retry triggering event is detected.

In step S320, the UE 105 detects a retry triggering event including, forexample, the UE 105 selecting a new PLMN; the UE 105 moving to a newRAT; the UE 105 switching off, or the SIM/USIM of the UE 105 beingremoved.

In step S325, as a result of detecting the retry triggering event instep S320, the UE 105 participates in a retry operation by sendinganother ESM request to the MME 160 and starts the timer T348x. The ESMrequest sent in step S320 may be of the same type as that describedabove with respect to step S305. Further, in the case that the retrytriggering event detected in step S320 is a RAT change indicating thatthe UE 105 is changing from the LTE network 150 to the GPRS network 110,the UE 105 sends the ESM message to the SGSN 170 in step S325, insteadof, sending the ESM request to the MME 160.

Accordingly, in the example shown in FIG. 3A, after receiving a ESMreject message from the MME 160 in step S310, the UE 105 does notattempt a retry operation by sending another ESM request message to theMME 160 until after a retry triggering event is detected in step S320.

In the example shown in FIG. 3A, no retry wait time is included in theESM reject message sent by the MME 160 in step S310. However, accordingto example embodiments, in addition to the retry triggering criteriadiscussed above with respect to FIG. 3A, the MME 160 can choose toprovide additional signaling indicating a retry wait time value to theUE 105 when the session management requests (PDN CONNECTIVITY REQUEST,BEARER RESOURCE ALLOCATION REQUEST, BEARER RESOURCE MODIFICATIONREQUEST) are rejected by the network and the network wants to restrictthe UE retry operations in a way that still allows a minimum of oneretry operation in a given time interval provided by the network. Inthis case, the MME 160 includes a value for ESM retry wait timer (e.g.value for timer T3497) in the ESM reject message and mobile retry of thesame ESM request is restricted by both the retry triggering criteria andthe retry wait time. Inclusion of the ESM retry wait timer in the ESMreject message is illustrated in FIG. 3B.

FIG. 3B illustrates a 4G EPC network example of providing UE retryrestriction using an ESM reject message with a ESM retry wait time.

As is shown in FIG. 3B, many of the operations in FIG. 3B are the sameas those shown in FIG. 3A. The operations shown in FIG. 3B differ fromthose shown in FIG. 3A as follows. After step S305, the MME 160 sends anESM reject message in step S312. The ESM reject message sent in stepS312 is the same as that described above with respect to step S310 withthe exception that the ESM reject message sent in step S312 additionallyincludes a ESM retry wait time value retryWaitTime. After step S312, instep S317 the UE 105 stops timer T348x and starts a ESM retry wait timer(e.g. timer T3497), which may be initialized by the UE 105 using thetimer value retryWaitTime received in step S312 via the ESM statusmessage. In the example shown in FIG. 3B, there are two types of eventswhich can permit the UE 105 to participate in a retry operation.

With respect to the first type of event, the UE 105 may detect atriggering event in step S320 in the same manner discussed above withrespect to FIG. 3A. If the triggering event is the UE changing RAT orPLMN, the ESM retry wait timer (e.g. timer T3497) is kept running instep S322. In case the trigger event is the UE switching off or the USIMremoval, the UE 105 stops the ESM retry wait timer (e.g. timer T3497) instep S322. Next, in step S325, the UE 105 sends an ESM request messagein the same manner discussed above with respect to FIG. 3A and startsthe timer T348x in step S325.

With respect to the second type of event, if the UE 105 determines thatthe ESM retry wait timer (e.g. timer T3497) expired before the UE 105detected any retry triggering event (S330), the UE does not performsteps S322 and S325, and, instead, the UE 105 starts the timer T348x instep S335 and attempts a retry operation by sending another ESM requestmessage to the MME 160 in step S340.

As used herein, the act of a UE starting/stopping the timer T3497 inassociation with an ESM request of a particular ESM request type for aparticular APN sent by the UE refers to the UE starting/stopping a T3497timer instance for the particular ESM request type and the particularAPN in a given PLMN.

According to one or more example embodiments, if the MME 160 receives,for example, from the UE 105, an EPS session management message withmessage type not defined or not implemented by the receiver and themessage is ignored, and if the MME 160 decides to return an ESM STATUSmessage with cause #97 “message type non-existent or not implemented”,then the MME 160 can choose to simply restrict the mobile retry of thesame ESM procedure based on a set of retry triggering criteriaincluding, for example, the mobile selecting a new PLMN; the mobilemoving to a new RAT; and the mobile switching off or universalsubscriber identity module (USIM) being removed. According to one ormore example embodiments, if any of the retry triggering condition ismet, the mobile can retry, as will be discussed in greater detail belowwith reference to FIG. 4A.

FIG. 4A illustrates a 4G EPC network example of providing UE retryrestriction using an ESM status message without a retry wait time.

Referring to FIG. 4A, in step S405 the UE 105 may initiate an ESMrequest start timer T348x and send an ESM request message to the MME160. The ESM request message may have a message type value of, forexample, PDN CONNECTIVITY REQUEST, BEARER RESOURCE ALLOCATION REQUEST,BEARER RESOURCE MODIFICATION REQUEST, PDN DISCONNECT REQUEST.

In step S410, the MME 160 may send an ESM status message to the UE 105.The ESM status message may have a ESM cause value of, “message typenon-existent or not implemented”. The ESM status message sent in stepS410 may not include a retry wait timer.

In step S415, the UE 105 stops timer T348x. According to one or moreexample embodiments, the UE 105 will not attempt a retry operation untila retry triggering event is detected.

In step S420, the UE 105 detects a retry triggering event including, forexample, the UE 105 selecting a new PLMN; the UE 105 moving to a newRAT; the UE 105 switching off, or the SIM/USIM of the UE 105 beingremoved.

In step S425, as a result of detecting the retry triggering event instep S420, the UE 105 participates in a retry operation by sendinganother ESM request to the MME 160 and starts the timer T348x. The ESMrequest sent in step S420 may be of the same type as that describedabove with respect to step S405. Further, in the case that the retrytriggering event detected in step S420 is a RAT change indicating thatthe UE 105 is changing from the LTE network 150 to the GPRS network 110,the UE 105 sends the ESM message to the SGSN 170 in step S425, insteadof, sending the ESM request to the MME 160.

Accordingly, in the example shown in FIG. 4A, after receiving a ESMstatus message from the MME 160 in step S410, the UE 105 does not sendanother ESM request message to the MME 160 until after a retrytriggering event is detected in step S420.

In the example shown in FIG. 4A, no retry wait time is included in theESM status message sent by the MME 160 in step S410. However, accordingto example embodiments, in addition to the retry triggering criteriadiscussed above with respect to FIG. 4A, the MME 160 can also choose toprovide additional signaling indicating a retry wait time value to theUE 105 if the network wants to restrict the mobile retry in a way tostill allows a minimum one retry operation in a given time intervalprovided by the network. In this case, the MME 160 includes a value forESM retry wait timer (e.g. timer T3497) in the ESM STATUS message andmobile retry of the same ESM request is restricted by both the retrytriggering criteria and the retry wait time. Inclusion of the retrytimer in the ESM status message is illustrated in FIG. 4B.

FIG. 4B illustrates a 4G EPC network example of providing UE retryrestriction using an ESM status message with a retry wait time.

As is shown in FIG. 4B, many of the operations in FIG. 4B are the sameas those shown in FIG. 4A. The operations shown in FIG. 4B differ fromthose shown in FIG. 4A as follows. After step S405, the MME 160 sends anESM status message in step S412. The ESM status message sent in stepS412 is the same as that described above with respect to step S410 withthe exception that the ESM status message sent in step S412 additionallyincludes a retry wait time value retryWaitTime. After step S412, in stepS417 the UE 105 stops timer T348x and starts a ESM retry wait timer(e.g. timer T3497), which may be initialized by the UE 105 using thetimer value retryWaitTime received in step S412 via the ESM statusmessage. In the example shown in FIG. 4B, there are two types of eventswhich can permit the UE 105 to participate in a retry operation.

With respect to the first type of event, the UE 105 may detect a retrytriggering event in step S420 in the same manner discussed above withrespect to FIG. 4A. If the triggering event is the UE changing RAT orPLMN, the ESM retry wait timer (e.g. timer T3497) is kept running instep S422. In case the trigger event is the UE switching off or the USIMremoval, the UE 105 stops the ESM retry wait timer (e.g. timer T3497) instep S422. Next, in step S425, the UE 105 sends an ESM request messagein the same manner discussed above with respect to FIG. 4A and startsthe timer T348x in step S425.

With respect to the second type of event, if the UE 105 determines thatthe ESM retry wait timer (e.g. timer T3497) expired before the UE 105detected any retry triggering event (S430), the UE does not performsteps S422 and S425, and, instead, the UE 105 starts the timer T348x instep S435 and sends another ESM request message to the MME 160 in stepS440.

In the examples for providing UE retry restriction for a 4G EPC networkdiscussed above with respect to FIGS. 3A-4B, a new ESM retry wait timervalue (e.g. timer value T3497) is introduced. According to one or moreexample embodiments, the ESM retry wait timer value (e.g. timer valueT3497) may have the attributes shown below in table 1.

TABLE 1 TIMER TIMER NORMAL NUM. VALUE STATE CAUSE OF START STOP T3497operator PROCEDURE PDN CONNECTIVITY UE is switched dependent,TRANSACTION REJECT, BEARER off or default 12 min PENDING RESOURCESIM/USIM is MODIFICATION REJECT, removed BEARER RESOURCE ALLOCATIONREJECT, ESM STATUS with a timer value for T3497 received

The value of ESM retry wait timer (e.g. timer T3497) can be provided byan operator communications network 100 operator when a request toestablish a packet data network (PDN) connection, a request to allocatebearer resources or a request to modify bearer resources is rejected bythe network with ESM cause #32 “service option not supported” or #33“requested service option not subscribed” or #8 (operator determinedbarring) or #27 (missing or unknown APN) or #97 “message typenon-existent or not implemented”, or when an ESM STATUS message isreceived. According to one or more example embodiments, the value of theESM retry wait timer (e.g. timer T3497) when included with ESM cause #32or #33 or #8 or #27 or #97 may be taken randomly or, alternatively,pseudo randomly, from an operator dependent range not greater than 72hours. If the PDN CONNECTIVITY REJECT was sent together with an ATTACHREQUEST message and the ATTACH REJECT message was not integrityprotected, a UE determining that value of the ESM retry wait timer (i.e.timer T3497) may use a random value from a default range of 15 mins to30 mins.

Accordingly, if the EPS session management (ESM) cause value is #32“service option not supported” or #33 “requested service option notsubscribed” or #8 (operator determined barring) or #27 (missing orunknown APN) or #97 “Message type non-existent or not implemented”, thenetwork may include a value for ESM retry wait timer (e.g. timer T3497)in the following messages:

PDN CONNECTIVITY REJECT message;BEARER RESOURCE ALLOCATION REJECT message; orBEARER RESOURCE MODIFICATION REJECT message.

If the EPS session management (ESM) cause value is #97 “Message typenon-existent or not implemented”, the network may include a value forESM retry wait timer (e.g. timer T3497) in the ESM STATUS message.

Tables 2-5 below show example contents of existing reject and statusmessages that are modified to include the ESM retry wait timer (i.e.timer T3497) according to one or more example embodiments. In tables2-5, the underlined text represents the modifications made to thecorresponding reject and status messages.

TABLE 2 PDN CONNECTIVITY REJECT message content Information IEI ElementType/Reference Presence Format Length . . . PDN connectivity Messagetype M V 1 reject message 9.8 identity . . . XX ESM Retry WaitGPRS timer 3 O TLV 3 Time value 9.9.3.16a (e.g. T3497 value)

TABLE 3 BEARER RESOURCE ALLOCATION REJECT message content InformationIEI Element Type/Reference Presence Format Length . . . Bearer resourceMessage type M V 1 allocation reject 9.8 message identity . . . XXESM Retry Wait GPRS timer 3 O TLV 3 Time  value 9.9.3.16a (e.g. T3497value)

TABLE 4 BEARER RESOURCE MODIFICATION REJECT message content InformationIEI Element Type/Reference Presence Format Length . . . Bearer resourceMessage type M V 1 modification 9.8 reject message identity . . . XXESM Retry Wait GPRS timer 3 O TLV 3 Time value 9.9.3.16a (e.g. T3497value)

TABLE 5 ESM STATUS message content Information IEI ElementType/Reference Presence Format Length . . . ESM status Message type M V1 message identity 9.8 . . . XX ESM Retry Wait GPRS timer 3 O TLV 3Time value 9.9.3.16a (e.g. T3497 value)

FIG. 5 is a flow chart illustrating an example of logic executed by a UEwhen handling a PDN CONNECTIVITY REJECT message in accordance with oneor more example embodiments.

Referring to FIG. 5, in step S505, the UE sends a PDN CONNECTIVITYREQUEST message, which is an ESM message, for example, to the MME 160.

In step S510, the UE 105 receives a PDN CONNECTIVITY REJECT message, forexample from the MME 160. The PDN CONNECTIVITY REJECT message mayindicate that the PDN CONNECTIVITY REQUEST message of step S505 wasrejected and may include an ESM cause value of, for example, #32“service option not supported” or #33 “requested service option notsubscribed” or #8 (operator determined barring) or #27 (missing orunknown APN) or #97 “message type non-existent or not implemented”.

In step S515, if an ESM retry wait time (e.g., a value for timer T3497)was included in the PDN CONNECTIVITY REJECT message, the UE 105 proceedsto step S520.

In step S520, if the PDN CONNECTIVITY REJECT message was sent with anATTACH REJECT message, the UE 105 proceeds to step S525.

In step S525, if the ATTACH REJECT message is not integrity protected,the UE 105 proceeds to step S530.

In step S530, the UE 105 starts the retry wait time with a random valueand does not initiate an attach procedure for the same APN as that forwhich the PDN CONNECTIVITY REQUEST of step S505 was sent until anearliest one of the following happens: a retry triggering event occurs(S550) or the retry wait timer expires (S535).

After step S530, if the UE 105 detects that the retry wait timer hasexpired (S535), the UE 105 proceeds to step S580.

In step S580, the UE 105 performs a retry operation by sending a PDNCONNECTIVITY REQUEST message, for example, to the MME 160. The PDNCONNECTIVITY REQUEST sent in step S580 may be sent for the same APN asthat for which the PDN CONNECTIVITY REQUEST of step S580 was sent.

After step S530, if the UE 105 detects that a retry triggering event hasoccurred (S550), the UE 105 proceeds to step S575A/S575B. As isillustrated in FIG. 5, the retry triggering event can be, for example,the UE 105 selecting a new PLMN (S555A), the UE 105 changing to a newRAT (S555B) or the UE 105 switching off or the SIM/USIM of the UE 105being removed (S555C).

In step S575A, the UE 105 keeps the retry wait timer for PDNCONNECTIVITY REQUEST request at previous RAT/PLMN running if the retrywait timer is running, and proceeds to step S580. In step S575B, the UE105 stops the retry wait timer if the retry wait timer is running, andproceeds to step S580.

If, in step S525, if the ATTACH REJECT message is integrity protected,the UE 105 proceeds to step S540.

In step S540, if the retry wait time value is not 0 or deactivated, theUE 105 proceeds to step S545.

In step S545, the UE starts the retry wait timer with the retry waittime value received in the PDN CONNECTIVITY REJECT message in step S510,and does not initiate an attach procedure with the same PDN CONNECTIVITYREQUEST message sent by the UE 105 in step S505 until an earliest one ofthe following happens: a retry triggering event occurs (S550) or theretry wait timer expires (S535).

If, in step S540, if the retry wait time value is 0 or deactivated, theUE 105 proceeds to step S560.

In step S560, if the retry wait time is not deactivated, the US 105proceeds to step S565 where the UE 105 can retry the same ESM messagesent in step S505 for example by sending, to the MME 160, a PDNCONNECTIVITY REQUEST for the same APN as that for which the PDNCONNECTIVITY REQUEST of step S505 was sent.

In step S560, if the retry wait time is deactivated, the UE 105 proceedsto step S570.

In step S570, the UE 105 waits for a retry triggering event to bedetected in step S550. In step S570, the UE 105 does not initiate anattach procedure for the same APN as that for which the PDN CONNECTIVITYREQUEST message of step S505 was sent until a retry triggering eventoccurs (S550).

If, in step S520, if the PDN CONNECTIVITY REJECT message was sentstandalone, the UE 105 proceeds to step S540.

If, in step S515, the retry wait time is not included in the PDNCONNECTIVITY REJECT message, the UE 105 proceeds to step S570.

FIG. 6 is a flow chart illustrating an example of logic executed by a UEwhen handling a BEARER RESOURCE ALLOCATION REJECT message in accordancewith one or more example embodiments.

Referring to FIG. 6, in step S605, the UE sends a BEARER RESOURCEALLOCATION REQUEST message, which is an ESM message, for example, to theMME 160.

In step S610, the UE 105 receives a BEARER RESOURCE ALLOCATION REJECTmessage, for example from the MME 160. The BEARER RESOURCE ALLOCATIONREJECT message may indicate that the BEARER RESOURCE ALLOCATION REQUESTmessage of step S605 was rejected, and may include an ESM cause valueof, for example, #32 “service option not supported” or #33 “requestedservice option not subscribed” or #8 (operator determined barring) or#27 (missing or unknown APN) or #97 “message type non-existent or notimplemented”.

In step S615, if an ESM retry wait time (e.g., a value for timer T3497)was included in the BEARER RESOURCE ALLOCATION REJECT message, the UE105 proceeds to step S620.

In step S620, if the retry wait time value is not 0 or deactivated, theUE 105 proceeds to step S660.

In step S660, the UE starts the retry wait timer with the retry waittime value received in the BEARER RESOURCE ALLOCATION REJECT message instep S610, and does not send another BEARER RESOURCE ALLOCATION REQUESTfor the same APN as that for which the BEARER RESOURCE ALLOCATIONREQUEST message of step S605 was sent until an earliest one of thefollowing happens: a retry triggering event occurs (S640) or the retrywait timer expires (S665).

After step S660, if the UE 105 detects that the retry wait timer hasexpired (S665), the UE 105 proceeds to step S655.

In step S655, the UE 105 performs a retry operation by sending a BEARERRESOURCE ALLOCATION REQUEST message, for example, to the MME 160. TheBEARER RESOURCE ALLOCATION REQUEST sent in step S655 may be sent for thesame APN as that for which the BEARER RESOURCE ALLOCATION REQUEST ofstep S605 was sent.

After step S660, if the UE 105 detects that a retry triggering event hasoccurred (S640), the UE 105 proceeds to step S650A/S650B. As isillustrated in FIG. 6, the retry triggering event can be, for example,the UE 105 selecting a new PLMN (S645A), the UE 105 changing to a newRAT (S645B) or the UE 105 switching off or the SIM/USIM of the UE 105being removed (S645C).

In step S650A, the UE 105 keeps the retry wait timer for BEARER RESOURCEALLOCATION REQUEST request at previous RAT/PLMN running if the retrywait timer is running, and proceeds to step S655. In step S650B, the UE105 stops the retry wait timer if the retry wait timer is running, andproceeds to step S655 described above.

In step S620, if the retry wait time value is 0 or deactivated, the UE105 proceeds to step S625.

In step S625, if the retry wait time is not deactivated, the UE 105proceeds to step S630 where the UE 105 can retry the same ESM messagesent in step S605 for example by sending, to the MME 160, a BEARERRESOURCE ALLOCATION REQUEST for the same APN as that for which theBEARER RESOURCE ALLOCATION REQUEST of step S705 was sent.

In step S625, if the retry wait time is deactivated, the UE 105 proceedsto step S635.

In step S635, the UE 105 waits for a retry triggering event to bedetected in step S640. In step S635, the UE 105 does not send anotherBEARER RESOURCE ALLOCATION REQUEST for the same APN as that for whichthe BEARER RESOURCE ALLOCATION REQUEST message of step S605 was sentuntil a retry triggering event occurs (S640). Step S640 is describedabove.

If, in step S615, the retry wait time is not included in the BEARERRESOURCE ALLOCATION REJECT message, the UE 105 proceeds to step S635described above.

FIG. 7 is a flow chart illustrating an example of logic executed by a UEwhen handling a BEARER RESOURCE MODIFICATION REJECT message inaccordance with one or more example embodiments.

Referring to FIG. 7, in step S705, the UE sends a BEARER RESOURCEMODIFICATION REQUEST message, which is an ESM message, for example, tothe MME 160.

In step S710, the UE 105 receives a BEARER RESOURCE MODIFICATION REJECTmessage, for example from the MME 160. The BEARER RESOURCE MODIFICATIONREJECT message may indicate that the BEARER RESOURCE MODIFICATIONREQUEST message of step S705 was rejected, and may include an ESM causevalue of, for example, #32 “service option not supported” or #33“requested service option not subscribed” or #8 (operator determinedbarring) or #27 (missing or unknown APN) or #97 “message typenon-existent or not implemented”.

In step S715, if an ESM retry wait time (e.g., a value for timer T3497)was included in the BEARER RESOURCE ALLOCATION REJECT message, the UE105 proceeds to step S720.

In step S720, if the ESM retry wait time value is not 0 or deactivated,the UE 105 proceeds to step S725.

In step S725, the UE starts the retry wait timer with the retry waittime value received in the BEARER RESOURCE MODIFICATION REJECT messagein step S710, and does not send another BEARER RESOURCE MODIFICATIONREQUEST for the same APN as that for which the BEARER RESOURCEMODIFICATION REQUEST message of step S705 was sent until an earliest oneof the following happens: a retry triggering event occurs (S755) or theretry wait timer expires (S730).

After step S725, if the UE 105 detects that the retry wait timer hasexpired (S730), the UE 105 proceeds to step S735.

In step S735, the UE 105 performs a retry operation by sending a BEARERRESOURCE MODIFICATION REQUEST message, for example, to the MME 160. TheBEARER RESOURCE MODIFICATION REQUEST sent in step S735 may be sent forthe same APN as that for which the BEARER RESOURCE MODIFICATION REQUESTof step S705 was sent.

After step S725, if the UE 105 detects that a retry triggering event hasoccurred (S755), the UE 105 proceeds to step S765A/S765B. As isillustrated in FIG. 7, the retry triggering event can be, for example,the UE 105 selecting a new PLMN (S760A), the UE 105 changing to a newRAT (S760B) or the UE 105 switching off or the SIM/USIM of the UE 105being removed (S760C).

In step S765A, the UE 105 keeps the retry wait timer for BEARER RESOURCEMODIFICATION REQUEST request at previous RAT/PLMN running if the retrywait timer is running, and proceeds to step S735. In step S765B, the UE105 stops the retry wait timer if the retry wait timer is running, andproceeds to step S735, which is described above.

In step S720, if the retry wait time value is 0 or deactivated, the UE105 proceeds to step S740.

In step S740, if the retry wait time is not deactivated, the UE 105proceeds to step S745 where the UE 105 can retry the same ESM messagesent in step S705, for example by sending, to the MME 160, a BEARERRESOURCE MODIFICATION REQUEST for the same APN as that for which theBEARER RESOURCE MODIFICATION REQUEST of step S705 was sent.

In step S740, if the retry wait time is deactivated, the UE 105 proceedsto step S750.

In step S750, the UE 105 waits for a retry triggering event to bedetected in step S755. In step S750, the UE 105 does not send anotherBEARER RESOURCE MODIFICATION REQUEST for the same APN as that for whichthe BEARER RESOURCE ALLOCATION REQUEST message of step S705 was sentuntil a retry triggering event occurs (S755). Step S755 is describedabove.

If, in step S715, the retry wait time is not included in the BEARERRESOURCE MODIFICATION REJECT message, the UE 105 proceeds to step S750,which is described above.

FIG. 8 is a flow chart illustrating an example of logic executed by a UEwhen handling a ESM STATUS message in accordance with one or moreexample embodiments.

Referring to FIG. 8, in step S805, the UE attempt an ESM procedure bysending an ESM request message, for example, to the MME 160. The ESMrequest message sent in step S805 may be, for example, a PDNCONNECTIVITY REQUEST, BEARER RESOURCE ALLOCATION REQUEST, or BEARERRESOURCE MODIFICATION REQUEST.

In step S810, the UE 105 receives a ESM STATUS message, for example fromthe MME 160. The ESM STATUS message may indicate that the ESM message ofstep S805 was rejected, and may include an ESM cause value of, forexample #97 “message type non-existent or not implemented”.

In step S815, if an ESM retry wait time (e.g., a value for timer T3497)was included in the ESM STATUS message, the UE 105 proceeds to stepS820.

In step S820, if the retry wait time value is not 0 or deactivated, theUE 105 proceeds to step S825.

In step S825, the UE starts the retry wait timer with the retry waittime value received in the ESM STATUS message in step S810, and does notreattempt the same ESM procedure as that associated with the ESM requestmessage sent in step S805 until an earliest one of the followinghappens: a retry triggering event occurs (S840) or the retry wait timerexpires (S830).

After step S825, if the UE 105 detects that the retry wait timer hasexpired (S830), the UE 105 proceeds to step S835.

In step S835, the UE 105 performs a retry operation by sending a ESMrequest message, for example, to the MME 160. The ESM request messagesent in step S835 may be associated with the same ESM procedure as thatwith which the ESM request message of step S805 is associated.

After step S825, if the UE 105 detects that a retry triggering event hasoccurred (S840), the UE 105 proceeds to step S850A/S850B. As isillustrated in FIG. 8, the retry triggering event can be, for example,the UE 105 selecting a new PLMN (S845A), the UE 105 changing to a newRAT (S845B) or the UE 105 switching off or the SIM/USIM of the UE 105being removed (S845C).

In step S850A, the UE 105 keeps the retry wait timer for rejected ESMrequest at previous RAT/PLMN running if the retry wait timer is running,and proceeds to step S835. In step S850B, the UE 105 stops the retrywait timer if the retry wait timer is running, and proceeds to stepS835, which is described above.

In step S820, if the retry wait time value is 0 or deactivated, the UE105 proceeds to step S855.

In step S855, if the retry wait timer is not deactivated, the UE 105proceeds to step S860 where the UE 105 can attempt a retry operation byattempting the same ESM procedure previously attempted in step S805, forexample, by resending the ESM message of step S805 to the MME 160.

In step S855, if the retry wait time is deactivated, the UE 105 proceedsto step S865.

In step S865, the UE 105 waits for a retry triggering event to bedetected in step S840. In step S865, the UE 105 does not retry the ESMprocedure attempted in step S805 until a retry triggering event occurs(S840). Step S840 is described above.

If, in step S815, the retry wait time is not included in the ESM STATUSmessage, the UE 105 proceeds to step S865, which is described above.

Providing UE Retry Restriction for GPRS Network

One or more example embodiments of providing UE retry restriction for aGPRS network will now be discussed below with reference to FIGS. 9-16and communications network 100 in FIG. 1.

When session management requests (ACTIVATE PDP CONTEXT REQUEST, ACTIVATESECONDARY PDP CONTEXT REQUEST or MODIFY PDP CONTEXT REQUEST) requestedby a mobile (e.g., the UE 105) by the network (e.g., the GPRS network110), and a reject message is sent back with SM cause #32 “serviceoption not supported”, #33 “requested service option not subscribed”, #8(operator determined barring), #27 (missing or unknown APN) or #97“message type non-existent or not implemented”, an SGSN (e.g., the SGSN120) can choose to simply restrict the mobile retry based on a set ofretry triggering criteria without consideration of retry wait time. Theretry triggering criteria may include, for example, when the mobileselecting a new PLMN; the mobile moving to a new RAT; the mobileswitching off or the SIM/USIM of the mobile being removed. According toone or more example embodiments, if any of the retry triggeringconditions are met, the mobile can retry, as will be discussed ingreater detail below with reference to FIG. 9.

FIG. 9 illustrates a GPRS network example of providing UE retryrestriction using an ESM reject message without a retry wait timeaccording to at least one example embodiment.

Referring to FIG. 9, in step S905 the UE 105 may initiate an SM request,start timer T338x and send an SM request message to the SGSN 120. The SMrequest message may have a message type value of, for example, ACTIVATEPDP CONTEXT REQUEST, ACTIVATE SECONDARY PDP CONTEXT REQUEST or MODIFYPDP CONTEXT REQUEST.

In step S910, the SGSN 120 may send an SM reject message to the UE 105.The SM reject message may have a message type value of, for example,ACTIVATE PDP CONTEXT REJECT, ACTIVATE SECONDARY PDP CONTEXT REJECT orMODIFY PDP CONTEXT REJECT. The SM reject message may have an SM causevalue of, for example, “service option not supported”, “requestedservice option not subscribed”, or “message type non-existent or notimplemented”. The SM reject message sent in step S910 may not include aretry wait timer.

In step S915, the UE 105 stops timer T338x. According to one or moreexample embodiments, the UE 105 will not attempt a retry operation untila retry triggering event is detected.

In step S920, the UE 105 detects a retry triggering event including, forexample, the UE 105 selecting a new PLMN; the UE 105 moving to a newRAT; the UE 105 switching off, or the SIM/USIM of the UE 105 beingremoved.

In step S925, as a result of detecting the retry triggering event instep S920, the UE 105 participates in a retry operation by sendinganother SM request to the SGSN 120 and starts the timer T338x. The SMrequest sent in step S920 may be of the same type as that describedabove with respect to step S905. Further, in the case that the retrytriggering event detected in step S920 is a RAT change indicating thatthe UE 105 is changing from the GPRS network 110 to the LTE network 150to the, the UE 105 sends an ESM message to the MME 160 in step S925,instead of, sending the SM request to the SGSN 120.

Accordingly, in the example shown in FIG. 9, after receiving a SM rejectmessage from the SGSN 120 in step S910, the UE 105 does not attempt aretry operation by sending another SM request message to the SGSN 120until after a retry triggering event is detected in step S920.

In the example shown in FIG. 9, no retry wait time is included in the SMreject message sent by the SGSN 120 in step S910. However, according toexample embodiments, in addition to the retry triggering criteriadiscussed above with respect to FIG. 10, the SGSN 120 can choose toprovide additional signaling indicating a retry wait time value to theUE 105 when the session management requests (ACTIVATE PDP CONTEXTREQUEST, ACTIVATE SECONDARY PDP CONTEXT REQUEST or MODIFY PDP CONTEXTREQUEST) are rejected by the network and the network wants to restrictthe UE retry operations in a way that still allows a minimum of oneretry operation in a given time interval provided by the network. Inthis case, the SGSN 120 includes a value for timer T3397 in the SMreject message and mobile retry of the same SM request is restricted byboth the retry triggering criteria and the retry wait time. Inclusion ofthe retry timer in the SM reject message is illustrated in FIG. 10.

FIG. 10 illustrates a GPRS network example of providing UE retryrestriction using an ESM reject message with a retry wait time accordingto at least one example embodiment.

As is shown in FIG. 10, many of the operations in FIG. 10 are the sameas those shown in FIG. 9. The operations shown in FIG. 10 differ fromthose shown in FIG. 9 as follows. After step S905, the SGSN 120 sends anSM reject message in step S912. The SM reject message sent in step S912is the same as that described above with respect to step S910 with theexception that the SM reject message sent in step S912 additionallyincludes a retry wait time value retryWaitTime. After step S912, in stepS917 the UE 105 stops timer T328x and starts a timer T3297, which may beinitialized by the UE 105 using the timer value retryWaitTime receivedin step S912 via the SM status message. In the example shown in FIG. 10,there are two types of events which can permit the UE 105 to participatein a retry operation.

With respect to the first type of event, the UE 105 may detect atriggering event in step S920 in the same manner discussed above withrespect to FIG. 9. In response to detecting the triggering event, the UE105 stops the timer T3297 and starts the timer T328x in step S922. Next,in step S925, the UE 105 sends an SM request message in the same mannerdiscussed above with respect to FIG. 9.

With respect to the second type of event, if the UE 105 determines thatthe ESM retry wait timer (e.g. timer T3497) expired before the UE 105detected any retry triggering event (S930), the UE does not performsteps S922 and S925, and, instead, the UE 105 starts the timer T328x instep S935 and attempts a retry operation by sending another SM requestmessage to the SGSN 120 in step S940.

According to one or more example embodiments, if the SGSN 120 receives,for example, from the UE 105, a session management message with messagetype not defined or not implemented by the receiver and the message isignored, and if the SGSN 120 decides to return an SM STATUS message withcause #97 “message type non-existent or not implemented”, then the SGSN120 can choose to simply restrict the mobile retry of the same SMprocedure based on a set of retry triggering criteria including, forexample, the mobile selecting a new PLMN; the mobile moving to a newRAT; and the mobile switching off or SIM/USIM being removed. Accordingto one or more example embodiments, if any of the retry triggeringcondition is met, the mobile can retry, as will be discussed in greaterdetail below with reference to FIG. 11.

FIG. 11 illustrates a GPRS network example of providing UE retryrestriction using an ESM status message without a retry wait timeaccording to at least one example embodiment.

Referring to FIG. 11, in step S1005 the UE 105 may initiate an SMrequest, start timer T338x and send an SM request message to the SGSN120. The SM request message may have a message type value of, forexample, ACTIVATE PDP CONTEXT REQUEST, ACTIVATE SECONDARY PDP CONTEXTREQUEST or MODIFY PDP CONTEXT REQUEST.

In step S1010, the SGSN 120 may send an SM status message to the UE 105.The SM status message may have a SM cause value of, “message typenon-existent or not implemented”. The SM status message sent in stepS1010 may not include a retry wait timer.

In step S1015, the UE 105 stops timer T338x. According to one or moreexample embodiments, the UE 105 will not attempt a retry operation untila retry triggering event is detected.

In step S1020, the UE 105 detects a retry triggering event including,for example, the UE 105 selecting a new PLMN; the UE 105 moving to a newRAT; the UE 105 switching off, or the SIM/USIM of the UE 105 beingremoved.

In step S1025, as a result of detecting the retry triggering event instep S1020, the UE 105 participates in a retry operation by sendinganother SM request to the SGSN 120 and starts the timer T338x. The SMrequest sent in step S1020 may be of the same type as that describedabove with respect to step S1005. Further, in the case that the retrytriggering event detected in step S1020 is a RAT change indicating thatthe UE 105 is changing from the GPRS network 110 to the LTE network 150,the UE 105 sends an ESM message to the MME 160 in step S1025, insteadof, sending the SM request to the SGSN 120.

Accordingly, in the example shown in FIG. 11, after receiving a SMstatus message from the SGSN 120 in step S1010, the UE 105 does not sendanother SM request message to the SGSN 120 until after a retrytriggering event is detected in step S1020.

In the example shown in FIG. 11, no retry wait time is included in theSM status message sent by the SGSN 120 in step S1010. However, accordingto example embodiments, in addition to the retry triggering criteriadiscussed above with respect to FIG. 11, the SGSN 120 can also choose toprovide additional signaling indicating a retry wait time value to theUE 105 if the network wants to restrict the mobile retry in a way tostill allows a minimum one retry operation in a given time intervalprovided by the network. In this case, the SGSN 120 includes a value fortimer T3397 in the SM STATUS message and mobile retry of the same SMrequest is restricted by both the retry triggering criteria and theretry wait time. Inclusion of the retry timer in the SM status messageis illustrated in FIG. 12.

FIG. 12 illustrates a GPRS network example of providing UE retryrestriction using an ESM status message with a retry wait time accordingto at least one example embodiment.

As is shown in FIG. 12, many of the operations in FIG. 12 are the sameas those shown in FIG. 11. The operations shown in FIG. 12 differ fromthose shown in FIG. 11 as follows. After step S1005, the SGSN 120 sendsan SM status message in step S1012. The SM status message sent in stepS1012 is the same as that described above with respect to step S1010with the exception that the SM status message sent in step S1012additionally includes a retry wait time value retryWaitTime. After stepS1012, in step S1017 the UE 105 stops timer T338x and starts a timerT3397, which may be initialized by the UE 105 using the timer valueretryWaitTime received in step S1012 via the SM status message. In theexample shown in FIG. 12, there are two types of events which can permitthe UE 105 to participate in a retry operation.

With respect to the first type of event, the UE 105 may detect a retrytriggering event in step S1020 in the same manner discussed above withrespect to FIG. 11. In response to detecting the retry triggering event,the UE 105 stops the timer T3397 and starts the timer T338x in stepS1022. Next, in step S1025, the UE 105 sends an SM request message inthe same manner discussed above with respect to FIG. 11.

With respect to the second type of event, if the UE 105 determines thatthe timer T3397 expired before the UE 105 detected any retry triggeringevent (S1030), the UE does not perform steps S1022 and S1025, and,instead, the UE 105 starts the timer T338x in step S1035 and sendsanother SM request message to the SGSN 120 in step S1040.

As used herein, the act of a UE starting/stopping the timer T3397 inassociation with an SM request of a particular SM request type for aparticular APN sent by the UE refers to the UE starting/stopping a T3397timer instance for the particular SM request type and the particular APNin a given PLMN.

In the examples for providing UE retry restriction for a GPRS networkdiscussed above with respect to FIGS. 9-12, a new timer value T3397 isintroduced. According to one or more example embodiments, the timervalue T3397 may have the attributes shown below in table 6.

TABLE 6 TIMER TIMER NORMAL NUM. VALUE STATE CAUSE OF START STOP T3397operator PDP- ACTIVATE PDP a new PLMN depend- ACT- CONTEXT REJECT, isselected, ent PEND ACTIVATE SECONDARY the MS has PDP CONTEXT REJECTchanged to a OR MODIFY PDP new RAT, the CONTEXT REJECT, SM MS is STATUSwith a timer switched off or value for T3397 received SIM/USIM isremoved

The value of timer T3397 can be provided by an operator ofcommunications network 100 when a request to activate a PDP context or arequest to modify a PDP context is rejected by the network with SM cause#32 “service option not supported” or #33 “requested service option notsubscribed” or #8 (operator determined barring) or #27 (missing orunknown APN) or #97 “message type non-existent or not implemented”, orwhen an SM STATUS message is received. According to one or more exampleembodiments, the value of the timer when included with SM cause #32,#33, #8, #27 or #97 may be taken randomly or, alternatively, pseudorandomly from an operator dependent range not greater than 72 hours.

Accordingly, if the session management (SM) cause value is #32 “serviceoption not supported” or #33 “requested service option not subscribed”or #8 (operator determined barring) or #27 (missing or unknown APN) or#97 “message type non-existent or not implemented”, the network mayinclude a value for timer T3397 in the following messages:

ACTIVATE PDP CONTEXT REJECT message;ACTIVATE SECONDARY PDP CONTEXT REJECT message; orMODIFY PDP CONTEXT REJECT message.

If the session management (SM) cause value is #97 “Message typenon-existent or not implemented”, the network may include a value fortimer T3397 in the SM STATUS message.

Tables 7-10 below show example contents of existing reject and statusmessages that are modified to include the ESM retry wait timer (e.g.timer T3497) according to one or more example embodiments. In tables2-5, the underlined text represents the modifications made to thecorresponding reject and status messages.

TABLE 7 ACTIVATE PDP CONTEXT REJECT message content Information IEIElement Type/Reference Presence Format Length . . . Activate PDP Messagetype M V 1 context reject 10.4 message identity . . . XX SM Retry WaitGPRS timer 3 O TLV 3 Time value 10.5.7.4a (e.g. T3397 value)

TABLE 8 ACTIVATE SECONDARY PDP CONTEXT REJECT message contentInformation IEI Element Type/Reference Presence Format Length . . .Bearer resource Message type M V 1 allocation reject 9.8 messageidentity . . . XX SM Retry Wait GPRS timer 3 O TLV 3 Time value10.5.7.4a (e.g. T3397 value)

TABLE 9 MODIFY PDP CONTEXT REJECT message content Information IEIElement Type/Reference Presence Format Length . . . Bearer resourceMessage type M V 1 modification 9.8 reject message identity . . . XXSM Retry Wait GPRS timer 3 O TLV 3 Time value 10.5.7.4a (e.g. T3397value)

TABLE 10 SM STATUS message content Information IEI ElementType/Reference Presence Format Length . . . ESM status Message type M V1 message identity 9.8 . . . XX SM Retry Wait GPRS timer 3 O TLV 3Time value 10.5.7.4a (e.g. T3397 value)

FIG. 13 is a flow chart illustrating an example of logic executed by aUE when handling an ACTIVATE PDP CONTEXT REJECT message in accordancewith one or more example embodiments.

Referring to FIG. 13, in step S1305, the UE attempts an SM procedure bysending an ACTIVATE PDP CONTEXT REQUEST message, which is an SM message,for example, to the SGSN 120.

In step S1310, the UE 105 receives an ACTIVATE PDP CONTEXT REJECTmessage, for example, from the SGSN 120. The ACTIVATE PDP CONTEXT REJECTmessage may indicate that the ACTIVATE PDP CONTEXT REQUEST message sentin step S1305 is rejected, and may include an SM cause value of, forexample, #32 “service option not supported”, #33 “requested serviceoption not subscribed”, #8 (operator determined barring), #27 (missingor unknown APN) or #97 “message type non-existent or not implemented”.

In step S1315, if a retry wait time (e.g., a value for timer T3397) wasincluded in the ACTIVATE PDP CONTEXT REJECT message, the UE 105 proceedsto step S1320.

In step S1320, if the retry wait time value is not 0 or deactivated, theUE 105 proceeds to step S1325.

In step S1325, the UE starts the retry wait timer with the retry waittime value received in the ACTIVATE PDP CONTEXT REJECT message in stepS1310, and does not send another ACTIVATE PDP CONTEXT REQUEST for thesame APN as that for which the ACTIVATE PDP CONTEXT REQUEST message ofstep S1305 was sent until an earliest one of the following happens: aretry triggering event occurs (S1340) or the retry wait timer expires(S1330).

After step S1325, if the UE 105 detects that the retry wait timer hasexpired (S1330), the UE 105 proceeds to step S1335.

In step S1335, the UE 105 performs a retry operation by sending anACTIVATE PDP CONTEXT REQUEST message, for example, to the SGSN 120. TheACTIVATE PDP CONTEXT REQUEST message sent in step S1335 may be sent forthe same APN as that for which the ACTIVATE PDP CONTEXT REQUEST messageof step S1335 was sent.

After step S1325, if the UE 105 detects that a retry triggering eventhas occurred (S1340), the UE 105 proceeds to step S1350A/S1350B. As isillustrated in FIG. 13, the retry triggering event can be, for example,the UE 105 selecting a new PLMN (S1345A), the UE 105 changing to a newRAT (S1345B) or the UE 105 switching off or the SIM/USIM of the UE 105being removed (S1345C).

In step S1350A, the UE 105 keeps the retry wait timer for ACTIVATE PDPCONTEXT REQUEST request at previous RAT/PLMN running if the retry waittimer is running, and proceeds to step S1335. In step S1350B, the UE 105stops the retry wait timer if the retry wait timer is running, andproceeds to step S1335, which is described above.

In step S1320, if the retry wait time value is 0 or deactivated, the UE105 proceeds to step S1355.

In step S1355, if the retry wait timer is not deactivated, the UE 105proceeds to step S1360 where the UE 105 can attempt a retry operation byattempting the same SM procedure previously attempted in step S1305, forexample by sending, to the SGSN 120 160, an ACTIVATE PDP CONTEXT REQUESTfor the same APN as that for which the ACTIVATE PDP CONTEXT REQUEST ofstep S1305 was sent.

In step S1355, if the retry wait time is deactivated, the UE 105proceeds to step S1365.

In step S1365, the UE 105 waits for a retry triggering event to bedetected in step S1340. In step S1365, the UE 105 does not send anotherACTIVATE PDP CONTEXT REQUEST for the same APN as that for which theACTIVATE PDP CONTEXT REQUEST message of step S1305 was sent until aretry triggering event occurs (S1340). Step S1340 is described above.

If, in step S1315, the retry wait time is not included in the ACTIVATEPDP CONTEXT REJECT message, the UE 105 proceeds to step S1365, which isdescribed above.

FIG. 14 is a flow chart illustrating an example of logic executed by aUE when handling an ACTIVATE SECONDARY PDP CONTEXT REJECT message inaccordance with one or more example embodiments.

Referring to FIG. 14, in step S1405, the UE 105 attempts an SM procedureby sending an ACTIVATE SECONDARY PDP CONTEXT REQUEST message, which isan SM message, for example, to the SGSN 120.

In step S1410, the UE 105 receives an ACTIVATE SECONDARY PDP CONTEXTREJECT message, for example, from the SGSN 120. The ACTIVATE SECONDARYPDP CONTEXT REJECT message may indicate that the ACTIVATE SECONDARY PDPCONTEXT REQUEST message sent in step S1405 is rejected, and may includean SM cause value of, for example, #32 “service option not supported”,#33 “requested service option not subscribed”, #8 (operator determinedbarring), #27 (missing or unknown APN) or #97 “message type non-existentor not implemented”.

In step S1415, if a retry wait time (e.g., a value for timer T3397) wasincluded in the ACTIVATE SECONDARY PDP CONTEXT REJECT message, the UE105 proceeds to step S1420.

In step S1420, if the retry wait time value is not 0 or deactivated, theUE 105 proceeds to step S1425.

In step S1425, the UE starts the retry wait timer with the retry waittime value received in the ACTIVATE SECONDARY PDP CONTEXT REJECT messagein step S1410, and does not send another ACTIVATE SECONDARY PDP CONTEXTREQUEST for the same APN as that for which the ACTIVATE SECONDARY PDPCONTEXT REQUEST message of step S1405 was sent until an earliest one ofthe following happens: a retry triggering event occurs (S1440) or theretry wait timer expires (S1430).

After step S1425, if the UE 105 detects that the retry wait timer hasexpired (S1430), the UE 105 proceeds to step S1435.

In step S1435, the UE 105 performs a retry operation by sending anACTIVATE SECONDARY PDP CONTEXT REQUEST message, for example, to the SGSN120. The ACTIVATE SECONDARY PDP CONTEXT REQUEST message sent in stepS1435 may be sent for the same APN as that for which the ACTIVATESECONDARY PDP CONTEXT REQUEST message of step S1435 was sent.

After step S1425, if the UE 105 detects that a retry triggering eventhas occurred (S1440), the UE 105 proceeds to step S1450A/S1450B. As isillustrated in FIG. 14, the retry triggering event can be, for example,the UE 105 selecting a new PLMN (S1445A), the UE 105 changing to a newRAT (S1445B) or the UE 105 switching off or the SIM/USIM of the UE 105being removed (S1445C).

In step S1450A, the UE 105 keeps the retry wait timer for ACTIVATESECONDARY PDP CONTEXT REQUEST request at previous RAT/PLMN running ifthe retry wait timer is running, and proceeds to step S1435. In stepS1450B, the UE 105 stops the retry wait timer if the retry wait timer isrunning, and proceeds to step S1435, which is described above.

In step S1420, if the retry wait time value is 0 or deactivated, the UE105 proceeds to step S1455.

In step S1455, if the retry wait timer is not deactivated, the UE 105proceeds to step S1460 where the UE 105 can attempt a retry operation byattempting the same SM procedure previously attempted in step S1405, forexample by sending, to the SGSN 120, an ACTIVATE SECONDARY PDP CONTEXTREQUEST for the same APN as that for which the ACTIVATE SECONDARY PDPCONTEXT REQUEST of step S1405 was sent.

In step S1455, if the retry wait time is deactivated, the UE 105proceeds to step S1465.

In step S1465, the UE 105 waits for a retry triggering event to bedetected in step S1440. In step S1465, the UE 105 does not send anotherACTIVATE SECONDARY PDP CONTEXT REQUEST for the same APN as that forwhich the ACTIVATE SECONDARY PDP CONTEXT REQUEST message of step S1405was sent until a retry triggering event occurs (S1440). Step S1440 isdescribed above.

If, in step S1415, the retry wait time is not included in the ACTIVATESECONDARY PDP CONTEXT REJECT message, the UE 105 proceeds to step S1465,which is described above.

FIG. 15 is a flow chart illustrating an example of logic executed by aUE when handling a MODIFY PDP CONTEXT REJECT message in accordance withone or more example embodiments.

Referring to FIG. 15, in step S1505, the UE 105 attempts an SM procedureby sending a MODIFY PDP CONTEXT REQUEST message, which is an SM message,for example, to the SGSN 120.

In step S1510, the UE 105 receives a MODIFY PDP CONTEXT REJECT message,for example, from the SGSN 120. The MODIFY PDP CONTEXT REJECT messagemay indicate that the MODIFY PDP CONTEXT REQUEST message sent in stepS1505 is rejected, and may include an SM cause value of, for example,#32 “service option not supported”, #33 “requested service option notsubscribed”, #8 (operator determined barring), #27 (missing or unknownAPN), or #97 “message type non-existent or not implemented”.

In step S1515, if a retry wait time (e.g., a value for timer T3397) wasincluded in the MODIFY PDP CONTEXT REJECT message, the UE 105 proceedsto step S1520.

In step S1520, if the retry wait time value is not 0 or deactivated, theUE 105 proceeds to step S1525.

In step S1525, the UE starts the retry wait timer with the retry waittime value received in the MODIFY PDP CONTEXT REJECT message in stepS1510, and does not send another MODIFY PDP CONTEXT REQUEST for the sameAPN as that for which the MODIFY PDP CONTEXT REQUEST message of stepS1505 was sent until an earliest one of the following happens: a retrytriggering event occurs (S1540) or the retry wait timer expires (S1530).

After step S1525, if the UE 105 detects that the retry wait timer hasexpired (S1530), the UE 105 proceeds to step S1535.

In step S1535, the UE 105 performs a retry operation by sending a MODIFYPDP CONTEXT REQUEST message, for example, to the SGSN 120. The MODIFYPDP CONTEXT REQUEST message sent in step S1535 may be sent for the sameAPN as that for which the MODIFY PDP CONTEXT REQUEST message of stepS1535 was sent.

After step S1525, if the UE 105 detects that a retry triggering eventhas occurred (S1540), the UE 105 proceeds to step S1550A/S1550B. As isillustrated in FIG. 15, the retry triggering event can be, for example,the UE 105 selecting a new PLMN (S1545A), the UE 105 changing to a newRAT (S1545B) or the UE 105 switching off or the SIM/USIM of the UE 105being removed (S1545C).

In step S1550A, the UE 105 keeps the retry wait timer for MODIFY PDPCONTEXT REQUEST request at previous RAT/PLMN running if the retry waittimer is running, and proceeds to step S1535. In step S1550B, the UE 105stops the retry wait timer if the retry wait timer is running, andproceeds to step S1535, which is described above.

In step S1520, if the retry wait time value is 0 or deactivated, the UE105 proceeds to step S1555.

In step S1555, if the retry wait timer is not deactivated, the UE 105proceeds to step S1560 where the UE 105 can attempt a retry operation byattempting the same SM procedure previously attempted in step S1505, forexample by sending, to the SGSN 120, a MODIFY PDP CONTEXT REQUEST forthe same APN as that for which the MODIFY PDP CONTEXT REQUEST of stepS1505 was sent.

In step S1555, if the retry wait time is deactivated, the UE 105proceeds to step S1565.

In step S1565, the UE 105 waits for a retry triggering event to bedetected in step S1540. In step S1565, the UE 105 does not send anotherMODIFY PDP CONTEXT REQUEST for the same APN as that for which the MODIFYPDP CONTEXT REQUEST message of step S1505 was sent until a retrytriggering event occurs (S1540). Step S1540 is described above.

If, in step S1515, the retry wait time is not included in the MODIFY PDPCONTEXT REJECT message, the UE 105 proceeds to step S1565, which isdescribed above.

FIG. 16 is a flow chart illustrating an example of logic executed by aUE when handling a SM STATUS message in accordance with one or moreexample embodiments.

Referring to FIG. 16, in step S1605, the UE attempt an SM procedure bysending an SM request message, for example, to the SGSN 120. The SMrequest message sent in step S1605 may be, for example, an ACTIVATE PDPCONTEXT REQUEST, ACTIVATE SECONDARY PDP CONTEXT REQUEST, ACTIVATE MBMSCONTEXT REQUEST, OR MODIFY PDP CONTEXT REQUEST.

In step S1610, the UE 105 receives a SM STATUS message, for example fromthe SGSN 120. The SM STATUS message may indicate that the SM message ofstep S1605 was rejected, and may include an SM cause value of, forexample #97 “message type non-existent or not implemented”.

In step S1615, if a retry wait time (e.g., a value for timer T3397) wasincluded in the SM STATUS message, the UE 105 proceeds to step S1620.

In step S1620, if the retry wait time value is not 0 or deactivated, theUE 105 proceeds to step S1625.

In step S1625, the UE starts the retry wait timer with the retry waittime value received in the SM STATUS message in step S1610, and does notretry the same SM procedure as that associated with the SM requestmessage sent in step S1605 until an earliest one of the followinghappens: a retry triggering event occurs (S1640) or the retry wait timerexpires (S1630).

After step S1625, if the UE 105 detects that the retry wait timer hasexpired (S1630), the UE 105 proceeds to step S1635.

In step S1635, the UE 105 performs a retry operation by sending a SMrequest message, for example, to the SGSN 120. The SM request messagesent in step S1635 may be associated with the same SM procedure as thatwith which the SM request message of step S1605 is associated.

After step S1625, if the UE 105 detects that a retry triggering eventhas occurred (S1640), the UE 105 proceeds to step S1650A/S1650B. As isillustrated in FIG. 16, the retry triggering event can be, for example,the UE 105 selecting a new PLMN (S1645A), the UE 105 changing to a newRAT (S1645B) or the UE 105 switching off or the SIM/USIM of the UE 105being removed (S1645C).

In step S1650A, the UE 105 keeps the retry wait timer for rejected SMrequest at previous RAT/PLMN running if the retry wait timer is running,and proceeds to step S1635. In step S1650B, the UE 105 stops the retrywait timer if the retry wait timer is running, and proceeds to stepS1635, which is described above.

In step S1620, if the retry wait time value is 0 or deactivated, the UE105 proceeds to step S1655.

In step S1655, if the retry wait timer is not deactivated, the UE 105proceeds to step S1660 where the UE 105 can attempt a retry operation byattempting the same SM procedure previously attempted in step S1605, forexample, by resending the SM message of step S1605 to the SGSN 120.

In step S1655, if the retry wait time is deactivated, the UE 105proceeds to step S1665.

In step S1665, the UE 105 waits for a retry triggering event to bedetected in step S1640. In step S1665, the UE 105 does not retry the SMprocedure attempted in step S1605 until a retry triggering event occurs(S1640). Step S1640 is described above.

If, in step S1615, the retry wait time is not included in the SM STATUSmessage, the UE 105 proceeds to step S1665, which is described above.

Providing UE Retry Restriction with a RAT Dependency Indication

Examples for providing UE retry restriction using retriggering events orretriggering events and retry timers are discussed above with referenceto FIGS. 3-16. As is explained above, in the examples discussed abovewith reference to FIGS. 3-16, if no wait time is included in a reject orstatus message received at the UE 105, the UE 105 may refrain fromperforming a retry operation until a retriggering event occurs. Further,if the UE 105 receives a wait time in a reject or status message, the UE105 may refrain from performing a retry operation until after theearlier of (i) a retriggering event occurring, and (ii) the retry waittimer expiring.

Further, according to at least some example embodiments, a wait timevalue may be configured in the UE 105 such that the UE 105 may alwaysrefrain from performing a retry operation until after the earlier of (i)a retriggering event occurring and (ii) the retry wait timer expiring,even if no wait timer is included in a reject of status message receivedat the UE. For example, as will be discussed in greater detail belowwith reference to FIGS. 17-26 b, if no wait timer value 105 is sent tothe UE 105 in a reject of status message, the UE 105 may initialize aretry wait timer using the wait time value configured in the UE.

Additionally, according to at least some example embodiments, the UE 105may operate in a RAT independent mode or a RAT dependent mode.

In the RAT independent mode, once an attempt by the UE 105 to perform afirst ESM or SM procedure is rejected in a first RAT (e.g., LTE orGPRS), the UE 105 does not attempt to perform an ESM or SM procedure ofthe same service type as the first ESM procedure in any RAT until afterthe earlier of (i) a retriggering event occurring and (ii) the retrywait timer expiring. For example, both GPRS and EPS RATs have particularRequest messages associated with the service of setting up a PDNconnection. Accordingly, ESM and SM request messages for setting up aPDN connection are examples of request messages of a first service type.Further, both GPRS and EPS RATs have particular Request messagesassociated with the service of establishing bearers within the PDNconnection. Accordingly, ESM and SM request messages for establishingbearers within the PDN connection are examples of request messages of asecond service type. Accordingly, as an example, if the UE 105 operatingin RAT independent mode sends an ESM Request with the message type PDNCONNECTIVITY REQUEST while attached to an EPS network, and the UE 105switches to a GPRS network thereafter, the UE 105 will restrict itselffrom sending an SM Request with the message type ACTIVATE PDP CONTEXTREQUEST until after the earlier of (i) a retriggering event occurringand (ii) the retry wait timer expiring. While in RAT independent mode,the UE 105 will operate in the manner discussed above because, despitebeing associated with different RATs (i.e., EPS and GPRS) the PDNCONNECTIVITY REQUEST ESM Request is considered to have the same servicetype as the ACTIVATE PDP CONTEXT REQUEST SM Request.

In the RAT dependent mode, once an attempt by the UE 105 to perform anESM or SM procedure is rejected in a first RAT (e.g., LTE or GPRS), theUE 105 can immediately attempt to perform the ESM or SM procedure oncein another RAT, even before (i) a retriggering event occurring and (ii)the retry wait timer expiring. For example, if an SM request messagesent by the UE 105 to the SGSN 120 is rejected, the UE 105 canimmediately attempt to send an ESM request message to the MME 160,without waiting for a retriggering event or the expiration of the retrytimer, even if the ESM request message corresponds to the same type ofprocedure as the SM request message.

As will be discussed in greater detail below with reference to FIGS.17-26B, a UE in communication network 100 may determine whether tooperate in RAT dependent mode or RAT independent mode based on thecontents of an SM/ESM reject or status message.

FIG. 17 illustrates a 4G EPC network example of providing UE retryrestriction using an RAT dependency indicator indicating an RATindependent mode and a retry wait time in an ESM reject message.

Referring to FIG. 17, in step S1705, a wait time is configured for theUE 105. The wait time may be configured in the UE 105 through, forexample, open mobile alliance (OMA) device management—(DM) protocolsignaling, non-access stratum (NAS) signaling, or configuration of auniversal integrated circuit card (UICC) included in the UE 105.

In step S1710 the UE 105 may initiate an ESM request, start timer T348xand send an ESM request message to the MME 160. The ESM request messagemay have a message type value of, for example, PDN CONNECTIVITY REQUEST,BEARER RESOURCE ALLOCATION REQUEST, or BEARER RESOURCE MODIFICATIONREQUEST.

In step S1715, the MME 160 may send an ESM reject message to the UE 105.The ESM reject message may have a message type value of, for example,PDN CONNECTIVITY REJECT, BEARER RESOURCE ALLOCATION REJECT, or BEARERRESOURCE MODIFICATION REJECT. The ESM reject message may have an ESMcause value of, for example, “service option not supported”, “requestedservice option not subscribed”, or “message type non-existent or notimplemented”. The ESM reject message sent in step S1715 may also includea retry wait time value retryWaitTime. Further, according to at leastsome example embodiments, the communications network 100 may employdynamic signaling to instruct the UE 105 to operate in a RAT dependentmode by including a RAT dependency indicator (e.g., RAT_dependent) inthe ESM reject message sent in step S1715. In addition to, or as analternative to, including a RAT dependency indicator in the ESM rejectmessage sent in step S1715, a RAT dependency mode of the UE 105 may beconfigured in the UE 105 through, for example, OMA-DM protocolsignaling, NAS signaling, or configuration of a UICC included in the UE105. In the example shown in FIG. 17, the UE 105 is configured with aRAT dependency mode type of RAT dependent. According to one or moreexample embodiments, an RAT dependency mode type configured in the UE105 may indicate a default RAT dependency mode which the UE 105 uses ifno RAT dependency indicator is included in the ESM reject message sentin step S1715.

In step S1720, the UE 105 stops timer T348x, and starts ESM retry waittimer (e.g. timer T3497) with the timer value retryWaitTime received instep S1715. According to one or more example embodiments, the UE 105will not attempt a retry operation until the earlier of (a) a retrytriggering event occurring (S1725), and (b) the ESM retry wait timerT3497 expiring (S1740).

With respect to (a) the retry triggering event, in step S1725, the UE105 detects a retry triggering event before the ESM retry wait timer(e.g. timer T3497) expires. The retry triggering event detected in stepS1725 may be, for example, the UE 105 selecting a new PLMN; the UE 105moving to a new RAT; the UE 105 switching off, or the SIM/USIM of the UE105 being removed.

As a result of detecting the retry triggering event in step S1725, theUE 105 performs steps S1730 and S1735.

In step S1730, if the triggering event is the UE changing RAT or PLMN,the ESM retry wait timer (e.g. timer T3497) is kept running. In case thetrigger event is the UE switching off or the USIM removal, the UE 105stops the ESM retry wait timer (e.g. timer T3497).

Further, in step S1735, the UE 105 participates in a retry operation bysending another ESM request to the MME 160 and starts the timer T348x.The ESM request sent in step S1735 may be of the same type as thatdescribed above with respect to step S1710. Further, in the case thatthe retry triggering event detected in step S1725 is a RAT changeindicating that the UE 105 is changing from the LTE network 150 to theGPRS network 110, the UE 105 sends an SM message to the SGSN 120 in stepS1735, instead of, sending the ESM request to the MME 160.

With respect to (b) the ESM retry timer expiring, if the UE 105determines that the ESM retry wait timer (e.g. timer T3497) expiredbefore the UE 105 detected any retry triggering event (S1740), the UE105 does not perform steps S1730 and S1735, and, instead, the UE 105starts the timer T348x in step S1745 and sends another ESM requestmessage to the MME 160 in step S1750.

Accordingly, in the example shown in FIG. 17, after receiving a ESMreject message from the MME 160 in step S1715, the UE 105 does notattempt a retry operation by sending another ESM request message to theMME 160 until after the earlier of (a) a retry triggering eventoccurring, and (b) the ESM retry wait timer (e.g. timer T3497) expiring.Further, the ESM reject message may indicate an RAT dependency mode inwhich the UE 105 is to operate.

FIG. 18 illustrates a 4G EPC network example of providing UE retryrestriction using an RAT dependency indicator indicating an RATdependent mode without a retry wait time in an ESM reject message.

As is shown in FIG. 18, many of the operations in FIG. 18 are the sameas those shown in FIG. 17. The operations shown in FIG. 18 differ fromthose shown in FIG. 17 as follows. After step S1710, in step S1815, theMME 160 sends an ESM reject message to the UE 105. The ESM rejectmessage sent in step S1815 is the same as that described above withrespect to step S1715 with the exception that the ESM reject messagesent in step S1815 does not include a retry wait time valueretryWaitTime. Further, after the UE 105 receives the ESM reject messagein step S1815, in step S1820, the UE 105 stops the timer T348x, andstarts the ESM retry wait timer (e.g. timer T3497) using, as the initialtimer value of the ESM retry wait timer (e.g. timer T3497), the timervalue configured in the UE 105 in step S1705. According to one or moreexample embodiments, after step S1820, in the same manner discussedabove with respect to FIG. 17, the UE 105 will not attempt a retryoperation until the earlier of (a) a retry triggering event occurring(S1725), and (b) the ESM retry wait timer (e.g. timer T3497) expiring(S1740).

FIG. 19 illustrates a 4G EPC network example of providing UE retryrestriction using a RAT dependency indicator indicating an RATindependent mode and a retry wait time value in an ESM reject message.

As is shown in FIG. 19, many of the operations in FIG. 19 are the sameas those shown in FIG. 17. The operations shown in FIG. 19 differ fromthose shown in FIG. 17 as follows. After step S1710, the MME 160 sendsan ESM reject message in step S1915. The ESM reject message sent in stepS1915 is the same as that described above with respect to step S1715with the exception that the ESM reject message sent in step S1915includes an RAT dependency indicator RAT_independent, which indicates anRAT independent mode. Further, step S1920 is the same as step S1720 withthe exception that, instead of starting ESM retry wait timer (e.g. timerT3497), in step S1920 the UE 105 starts retry wait timer T3396. In stepS1920, the UE 105 may start the timer T3396 using the timer valueretryWaitTime included in the ESM reject message received in step S1915.Step S1925 may be the same as step S1725 with the exception that the UE105 changing to a new RAT is no longer a retry triggering event. Forexample, because, in FIG. 19, the UE 105 is operating in the RATindependent mode, the UE 105 does not perform a retry operation simplybecause the UE 105 changes RATs. Further, step S1930 may be the same asstep S1730 with the exception that the retry wait timer T3396 is used instep S1930 instead of the ESM retry wait timer (e.g. timer T3497).Further, step S1935 may be the same as step S1735 with the exceptionthat no ESM request message is sent from the UE 105 to the SGSN 120because, as is discussed above, in RAT independent mode, changing theRAT of the UE 105 is not a retry triggering event. Further, step S1940,is the same as step S1740 with the exception that step S1940 takes placewhen the retry timer T3396 expires. Accordingly, the UE 105 will notattempt a retry operation until the earlier of (a) a retry triggeringevent occurring (S1925), and (b) the retry wait timer T3396 expiring(S1940).

As used herein, the act of a UE starting/stopping the timer T3396 inassociation with an ESM/SM request of a particular ESM/SM request typefor a particular APN sent by the UE refers to the UE starting/stopping aT3396 timer instance for the particular ESM/SM request type and theparticular APN in a given PLMN.

FIG. 20 illustrates a 4G EPC network example of providing UE retryrestriction using a RAT dependency indicator indicating an RATindependent mode and no retry wait time value in an ESM reject message.

As is shown in FIG. 20, many of the operations in FIG. 20 are the sameas those shown in FIG. 19. The operations shown in FIG. 20 differ fromthose shown in FIG. 19 as follows. After step S1710, in step S2015, theMME 160 sends an ESM reject message to the UE 105. The ESM rejectmessage sent in step S2015 is the same as that described above withrespect to step S1915 with the exception that the ESM reject messagesent in step S2015 does not include a retry wait time valueretryWaitTime. Further, after the UE 105 receives the ESM reject messagein step S2015, in step S2020, the UE 105 stops the timer T348x, andstarts the timer T3396 using, as the initial timer value of the timerT3396, the timer value configured in the UE 105 in step S1705. Accordingto one or more example embodiments, after step S2020, in the same mannerdiscussed above with respect to FIG. 19, the UE 105 will not attempt aretry operation until the earlier of (a) a retry triggering eventoccurring (S1925), and (b) the retry wait timer T3396 expiring (S1940).

FIGS. 21A and 21B illustrate 4G EPC network examples of providing UEretry restriction using the absence or presence of a retry wait timevalue in an ESM reject message as a RAT dependency indicator indicatingan RAT independent mode.

Referring to FIG. 21A, in step S2105, a wait time is configured for theUE 105. The wait time may be configured in the UE 105 through, forexample, OMA-DM protocol signaling, NAS signaling, or configuration of aUICC included in the UE 105.

In step S2110 the UE 105 may initiate an ESM request start timer T348xand send an ESM request message to the MME 160. The ESM request messagemay have a message type value of, for example, PDN CONNECTIVITY REQUEST,BEARER RESOURCE ALLOCATION REQUEST, or BEARER RESOURCE MODIFICATIONREQUEST.

In step S2115, the MME 160 may send an ESM reject message to the UE 105.The ESM reject message may have a message type value of, for example,PDN CONNECTIVITY REJECT, BEARER RESOURCE ALLOCATION REJECT, or BEARERRESOURCE MODIFICATION REJECT. The ESM reject message may have an ESMcause value of, for example, “service option not supported”, “requestedservice option not subscribed”, or “message type non-existent or notimplemented”. The ESM reject message sent in step S2115 may not includea retry wait time value retryWaitTime. According to at least someexample embodiments, in the example shown in FIG. 21A, when the UE 105receives the ESM reject message not including the retry wait time instep S2115, the UE 105 may interpret the absence of the retry wait timein the ESM reject message as an indication that the UE 105 is to operatein the RAT dependent mode.

In step S2120, the UE 105 stops timer T348x, and starts ESM retry waittimer (e.g. timer T3497) with the retry wait time value configured inthe UE 105 in step S2105. According to one or more example embodiments,the UE 105 will not attempt a retry operation until the earlier of (a) aretry triggering event occurring (S2125), and (b) the ESM retry waittimer (e.g. timer T3497) expiring (S2140).

With respect to (a) the retry triggering event, in step S2125, the UE105 detects a retry triggering event before the ESM retry wait timer(e.g. timer T3497) expires. The retry triggering event detected in stepS2125 may be, for example, the UE 105 selecting a new PLMN; the UE 105moving to a new RAT; the UE 105 switching off, or the SIM/USIM of the UE105 being removed.

As a result of detecting the retry triggering event in step S2125, theUE 105 performs steps S2130 and S2135.

In step S2130, if the triggering event is the UE changing RAT or PLMN,the ESM retry wait timer (e.g. timer T3497) is kept running. In case thetrigger event is the UE switching off or the USIM removal, the UE 105stops the ESM retry wait timer (e.g. timer T3497).

Further, in step S2135, the UE 105 participates in a retry operation bysending another ESM request to the MME 160 and starts the timer T348x.The ESM request sent in step S2135 may be of the same type as thatdescribed above with respect to step S2110. Further, in the case thatthe retry triggering event detected in step S2125 is a RAT changeindicating that the UE 105 is changing from the LTE network 150 to theGPRS network 110, the UE 105 sends an SM message to the SGSN 120 in stepS2135, instead of, sending the ESM request to the MME 160.

With respect to (b) the ESM retry timer expiring, if the UE 105determines that the ESM retry wait timer (e.g. timer T3497) expiredbefore the UE 105 detected any retry triggering event (S2140), the UE105 does not perform steps S2130 and S2135, and, instead, the UE 105starts the timer T348x in step S2145 and sends another ESM requestmessage to the MME 160 in step S2150.

Accordingly, in the example shown in FIG. 21A, after receiving a ESMreject message from the MME 160 in step S2115, the UE 105 does notattempt a retry operation by sending another ESM request message to theMME 160 until after the earlier of (a) a retry triggering eventoccurring, and (b) the ESM retry wait timer (e.g. timer T3497) expiring.Further, the absence of the retry timer value retryWaitTime from the ESMreject message may indicate that the UE 105 is to operate in the RATdependent mode.

As is shown in FIG. 21B, many of the operations in FIG. 21B are the sameas those shown in FIG. 21A. The operations shown in FIG. 21B differ fromthose shown in FIG. 21A as follows. After step S2110, the MME 160 sendsan ESM reject message to the UE 105 in step S2117. The ESM rejectmessage sent in step S2117 may be the same as the ESM message S2115 withthe exception that the ESM message sent in step S2117 includes a retrytimer retryWaitTime. According to at least some example embodiments, inthe example shown in FIG. 21B, when the UE 105 receives the ESM rejectmessage including the retry wait time value retryWaitTime in step S2115,the UE 105 may interpret the presence of the retry wait time value inthe ESM reject message as an indication that the UE 105 is to operate inthe RAT independent mode. Step S2122 may be the same as step S2120 withthe exception that the UE 105 starts the retry timer T3396 instead ofthe ESM retry wait timer (e.g. timer T3497). Further, in step S2122,instead of using the timer value configured in the UE 105 in step S2105,the UE 105 starts the retry timer T3396 using the timer valueretryWaitTime included in the ESM reject message received by the UE 105in step S2117. Step S2127 may be the same as step S2125 with theexception that the UE 105 changing to a new RAT is no longer a retrytriggering event. For example, because, in FIG. 21B, the UE 105 isoperating in the RAT independent mode, the UE 105 does not perform aretry operation simply because the UE 105 changes RATs. Further, stepS2132 may be the same as step S2130 with the exception that the timerT3396 is used in step S2132 instead of the ESM retry wait timer (e.g.timer T3497). Further, step S2137 may be the same as step S2135 with theexception that no ESM request message is sent from the UE 105 to theSGSN 120 because, as is discussed above, in RAT independent mode,changing the RAT of the UE 105 is not a retry triggering event. Further,step S2142 is the same as step S2140 with the exception that step S2142takes place when the retry timer T3396 expires. Accordingly, in FIG.21B, the UE 105 will not attempt a retry operation until the earlier of(a) a retry triggering event occurring (S2127), and (b) the retry waittimer T3396 expiring (S2140).

FIG. 22 illustrates a GPRS network example of providing UE retryrestriction using an RAT dependency indicator indicating an RATindependent mode and a retry wait time in an SM reject message.

Referring to FIG. 22, in step S2205, a wait time is configured for theUE 105. The wait time may be configured in the UE 105 through, forexample, OMA-DM protocol signaling, NAS signaling, or configuration of aUICC included in the UE 105.

In step S2210 the UE 105 may initiate an SM request, start timer T338xand send an SM request message to the SGSN 120. The SM request messagemay have a message type value of, for example, ACTIVATE PDP CONTEXTREQUEST, ACTIVATE SECONDARY PDP CONTEXT REQUEST, OR MODIFY PDP CONTEXTREQUEST.

In step S2215, the SGSN 120 may send an SM reject message to the UE 105.The SM reject message may have a message type value of, for example,ACTIVATE PDP CONTEXT REJECT, ACTIVATE SECONDARY PDP CONTEXT REJECT, ORMODIFY PDP CONTEXT REJECT. The SM reject message may have an SM causevalue of, for example, “service option not supported”, “requestedservice option not subscribed”, or “message type non-existent or notimplemented”. The SM reject message sent in step S2215 may also includea retry wait time value retryWaitTime. Further, according to at leastsome example embodiments, the communications network 100 may employdynamic signaling to instruct the UE 105 to operate in a RAT dependentmode by including a RAT dependency indicator RAT_dependent in the SMreject message sent in step S2215. In addition to, or as an alternativeto, including a RAT dependency indicator in the SM reject message sentin step S2215, an RAT dependency mode of the UE 105 may be configured inthe UE 105 through, for example, OMA-DM protocol signaling, NASsignaling, or configuration of a UICC included in the UE 105. In theexample shown in FIG. 22, the UE 105 is configured with a RAT dependencymode type of RAT dependent. According to one or more exampleembodiments, an RAT dependency mode type configured in the UE 105 mayindicate a default RAT dependency mode which the UE 105 uses if no RATdependency indicator is included in the SM reject message sent in stepS2215.

In step S2220, the UE 105 stops timer T338x, and starts timer T3397 withthe timer value retryWaitTime received in step S2215. According to oneor more example embodiments, the UE 105 will not attempt a retryoperation until the earlier of (a) a retry triggering event occurring(S2225), and (b) the retry wait timer T3397 expiring (S2240).

With respect to (a) the retry triggering event occurring, in step S2225,the UE 105 detects a retry triggering event before the retry wait timerT3397 expires. The retry triggering event detected in step S2225 may be,for example, the UE 105 selecting a new PLMN; the UE 105 moving to a newRAT; the UE 105 switching off, or the SIM/USIM of the UE 105 beingremoved.

As a result of detecting the retry triggering event in step S2225, theUE 105 performs steps S2230 and S2235.

In step S2230, the UE 105 stops the timer T3397 and starts the timerT338x.

Further, in step S2235, the UE 105 participates in a retry operation bysending another SM request to the SGSN 120. The SM request sent in stepS2235 may be of the same type as that described above with respect tostep S2210. Further, in the case that the retry triggering eventdetected in step S2225 is a RAT change indicating that the UE 105 ischanging from the GPRS network 110 to the LTE network 150, the UE 105sends an ESM message to the MME 160 in step S2235, instead of, sendingthe SM request to the SGSN 120.

With respect to (b) the ESM retry timer expiring, if the UE 105determines that the ESM retry wait timer (e.g. timer T3397) expiredbefore the UE 105 detected any retry triggering event (S2240), the UE105 does not perform steps S2230 and S2235, and, instead, the UE 105starts the timer T338x in step S2245 and sends another ESM requestmessage to the MME 160 in step S2250.

Accordingly, in the example shown in FIG. 22, after receiving a SMreject message from the SGSN 120 in step S2215, the UE 105 does notattempt a retry operation by sending another SM request message to theSGSN 120 until after the earlier of (a) a retry triggering eventoccurring, and (b) the retry wait timer T3397 expiring. Further, the SMreject message may indicate an RAT dependency mode in which the UE 105is to operate.

FIG. 23 illustrates a GPRS network example of providing UE retryrestriction using an RAT dependency indicator indicating an RATdependent mode without a retry wait time in an SM reject message.

As is shown in FIG. 23, many of the operations in FIG. 23 are the sameas those shown in FIG. 22. The operations shown in FIG. 23 differ fromthose shown in FIG. 22 as follows. After step S2210, in step S2315, theSGSN 120 sends an SM reject message to the UE 105. The SM reject messagesent in step S2315 is the same as that described above with respect tostep S2215 with the exception that the SM reject message sent in stepS2315 does not include a retry wait time value retryWaitTime. Further,after the UE 105 receives the SM reject message in step S2315, in stepS2320, the UE 105 stops the timer T338x, and starts the timer T3397using, as the initial timer value of the timer T3397, the timer valueconfigured in the UE 105 in step S2205. According to one or more exampleembodiments, after step S2320, in the same manner discussed above withrespect to FIG. 22, the UE 105 will not attempt a retry operation untilthe earlier of (a) a retry triggering event occurring (S2225), and (b)the retry wait timer T3397 expiring (S2240).

FIG. 24 illustrates a GPRS network example of providing UE retryrestriction using a RAT dependency indicator indicating an RATindependent mode and a retry wait time value in an SM reject message.

As is shown in FIG. 24, many of the operations in FIG. 24 are the sameas those shown in FIG. 22. The operations shown in FIG. 24 differ fromthose shown in FIG. 22 as follows. After step S2210, the SGSN 120 sendsan SM reject message in step S2415. The SM reject message sent in stepS2415 is the same as that described above with respect to step S2215with the exception that the SM reject message sent in step S2415includes an RAT dependency indicator RAT_independent, which indicates anRAT independent mode. Further, step S2420 is the same as step S2220 withthe exception that, instead of starting retry wait timer T3397, in stepS2420 the UE 105 starts retry wait timer T3396. In step S2420, the UE105 may start the timer T3396 using the timer value retryWaitTimeincluded in the SM reject message received in step S2415. Step S2425 maybe the same as step S2225 with the exception that the UE 105 changing toa new RAT is no longer a retry triggering event. For example, because,in FIG. 24, the UE 105 is operating in the RAT independent mode, the UE105 does not perform a retry operation simply because the UE 105 changesRATs. Further, step S2430 may be the same as step S2230 with theexception that the timer T3396 is used in step S2430 instead of thetimer T3397. Further, step S2435 may be the same as step S2235 with theexception that no SM request message is sent from the UE 105 to the SGSN120 because, as is discussed above, in RAT independent mode, changingthe RAT of the UE 105 is not a retry triggering event. Further, stepS2440, is the same as step S2240 with the exception that step S2440takes place when the retry timer T3396 expires. Accordingly, the UE 105will not attempt a retry operation until the earlier of (a) a retrytriggering event occurring (S2425), and (b) the retry wait timer T3396expiring (S2440).

FIG. 25 illustrates a GPRS network example of providing UE retryrestriction using a RAT dependency indicator indicating an RATindependent mode and no retry wait time value in an SM reject message.

As is shown in FIG. 25, many of the operations in FIG. 25 are the sameas those shown in FIG. 24. The operations shown in FIG. 25 differ fromthose shown in FIG. 24 as follows. After step S2210, in step S2515, theSGSN 120 sends an SM reject message to the UE 105. The SM reject messagesent in step S2515 is the same as that described above with respect tostep S2415 with the exception that the SM reject message sent in stepS2515 does not include a retry wait time value retryWaitTime. Further,after the UE 105 receives the SM reject message in step S2515, in stepS2520, the UE 105 stops the timer T338x, and starts the timer T3396using, as the initial timer value of the timer T3396, the timer valueconfigured in the UE 105 in step S2205. According to one or more exampleembodiments, after step S2520, in the same manner discussed above withrespect to FIG. 24, the UE 105 will not attempt a retry operation untilthe earlier of (a) a retry triggering event occurring (S2425), and (b)the retry wait timer T3396 expiring (S2440).

FIGS. 26A and 26B illustrate GPRS network examples of providing UE retryrestriction using the absence or presence of a retry wait time value inan SM reject message as a RAT dependency indicator indicating an RATindependent mode.

Referring to FIG. 26A, in step S2605, a wait time is configured for theUE 105. The wait time may be configured in the UE 105 through, forexample, OMA-DM protocol signaling, NAS signaling, or configuration of aUICC included in the UE 105.

In step S2610 the UE 105 may initiate an SM request, start timer T338xand send an SM request message to the SGSN 120. The SM request messagemay have a message type value of, for example, ACTIVATE PDP CONTEXTREQUEST, ACTIVATE SECONDARY PDP CONTEXT REQUEST, OR MODIFY PDP CONTEXTREQUEST.

In step S2615, the SGSN 120 may send an SM reject message to the UE 105.The SM reject message may have a message type value of, for example,ACTIVATE PDP CONTEXT REJECT, ACTIVATE SECONDARY PDP CONTEXT REJECT, ORMODIFY PDP CONTEXT REJECT. The SM reject message may have an SM causevalue of, for example, “service option not supported”, “requestedservice option not subscribed”, or “message type non-existent or notimplemented”. The SM reject message sent in step S2615 may not include aretry wait time value retryWaitTime. According to at least some exampleembodiments, in the example shown in FIG. 26A, when the UE 105 receivesthe SM reject message not including the retry wait time in step S2615,the UE 105 may interpret the absence of the retry wait time in the SMreject message as an indication that the UE 105 is to operate in the RATdependent mode.

In step S2620, the UE 105 stops timer T338x, and starts retry timerT3397 with the retry wait time value configured in the UE 105 in stepS2605. According to one or more example embodiments, the UE 105 will notattempt a retry operation until the earlier of (a) a retry triggeringevent occurring (S2625), and (b) the retry wait timer T3397 expiring(S2640).

With respect to (a) the retry triggering event occurring, in step S2625,the UE 105 detects a retry triggering event before the retry wait timerT3397 expires. The retry triggering event detected in step S2625 may be,for example, the UE 105 selecting a new PLMN; the UE 105 moving to a newRAT; the UE 105 switching off, or the SIM/USIM of the UE 105 beingremoved.

As a result of detecting the retry triggering event in step S2625, theUE 105 performs steps S2630 and S2635.

In step S2630, the UE 105 stops the timer T3397 and starts the timerT338x.

Further, in step S2635, the UE 105 participates in a retry operation bysending another SM request to the SGSN 120. The SM request sent in stepS2635 may be of the same type as that described above with respect tostep S2610. Further, in the case that the retry triggering eventdetected in step S2625 is a RAT change indicating that the UE 105 ischanging from the GPRS network 110 to the LTE network 150, the UE 105sends an ESM message to the MME 160 in step S2635, instead of, sendingthe SM request to the SGSN 120.

With respect to (b) the ESM retry timer expiring, if the UE 105determines that the ESM retry wait timer (e.g. timer T3396) expiredbefore the UE 105 detected any retry triggering event (S2640), the UE105 does not perform steps S2630 and S2635, and, instead, the UE 105starts the timer T338x in step S2645 and sends another ESM requestmessage to the MME 160 in step S2650.

Accordingly, in the example shown in FIG. 26A, after receiving a SMreject message from the SGSN 120 in step S2615, the UE 105 does notattempt a retry operation by sending another SM request message to theSGSN 120 until after the earlier of (a) a retry triggering eventoccurring, and (b) the retry wait timer T3397 expiring. Further, theabsence of the retry timer value retryWaitTime from the SM rejectmessage may indicate that the UE 105 is to operate in the RAT dependentmode.

As is shown in FIG. 26B, many of the operations in FIG. 26B are the sameas those shown in FIG. 26A. The operations shown in FIG. 26B differ fromthose shown in FIG. 26A as follows. After step S2610, the SGSN 120 sendsan SM reject message to the UE 105 in step S2617. The SM reject messagesent in step S2617 may be the same as the SM message S2615 with theexception that the SM message sent in step S2617 includes a retry timerretryWaitTime. According to at least some example embodiments, in theexample shown in FIG. 26B, when the UE 105 receives the SM rejectmessage including the retry wait time value retryWaitTime in step S2615,the UE 105 may interpret the presence of the retry wait time value inthe SM reject message as an indication that the UE 105 is to operate inthe RAT independent mode. Step S2622 may be the same as step S2620 withthe exception that the UE 105 starts the retry timer T3396 instead ofthe retry timer T3397. Further, in step S2622, instead of using thetimer value configured in the UE 105 in step S2605, the UE 105 startsthe retry timer T3396 using the timer value retryWaitTime included inthe SM reject message received by the UE 105 in step S2617. Step S2627may be the same as step S2625 with the exception that the UE 105changing to a new RAT is no longer a retry triggering event. Forexample, because, in FIG. 26B, the UE 105 is operating in the RATindependent mode, the UE 105 does not perform a retry operation simplybecause the UE 105 changes RATs. Further, step S2632 may be the same asstep S2630 with the exception that the timer T3396 is used in step S2632instead of the timer T3397. Further, step S2637 may be the same as stepS2635 with the exception that no SM request message is sent from the UE105 to the SGSN 120 because, as is discussed above, in RAT independentmode, changing the RAT of the UE 105 is not a retry triggering event.Further, step S2642 is the same as step S2640 with the exception thatstep S2642 takes place when the retry timer T3396 expires. Accordingly,in FIG. 26B, the UE 105 will not attempt a retry operation until theearlier of (a) a retry triggering event occurring (S2627), and (b) theretry wait timer T3396 expiring (S2640).

FIGS. 3B, 4B, 10, 12, and 17-26 are described above with reference to anexample in which a retry wait timer of UE 105 is kept running after theUE 105 detects a retry triggering event, which may be the UE 105selecting a new PLMN, or the UE 105 selecting a new RAT., the UE 105being switched off, or a SIM/USIM of the UE 105 being removed.

according to one or more example embodiments, if the retry wait time ofthe UE 105 is running when a retry triggering event is detected, and theretry triggering event is the UE 105 selecting a new PLMN or the UE 105selecting a new RAT, the retry wait timer is not stopped, and the retrywait timer (which, in the present scenario, was started by the UE 105when the UE 105 was connected to a previous PLMN or RAT) is allowed bythe UE 105 to continue running. In the present alternate embodiment, theretry wait timer of the UE is stopped after the UE 105 detects a retrytriggering event if the detected retry triggering event is the UE 105being switched off or a SIM/USIM of the UE 105 being removed.

Example embodiments being thus described, it will be obvious thatembodiments may be varied in many ways. Such variations are not to beregarded as a departure from example embodiments, and all suchmodifications are intended to be included within the scope of exampleembodiments.

What is claimed:
 1. A method of operating a user equipment (UE) in awireless communications network, the method comprising: sending, fromthe UE to a first network element, a first packet service sessionmanagement request message indicating a request of a first sessionmanagement service type for at least one of establishing a new packetdata session or modifying an existing packet data session, the firstpacket service session management request message being sent towards afirst access point name (APN); receiving, at the UE, a rejectionmessage, the rejection message indicating the request of the firstsession management service type has been rejected; and performing aretry operation after receiving the rejection message, the retryoperation including sending, from the UE, a second packet servicesession management request message of the first session managementservice type towards the first APN, the retry operation being preventedby the UE such that the retry operation is not performed by the UE untilafter at least one of, an expiration of a retry timer of the UE, ordetection, at the UE, of a retry trigger event.
 2. The method of claim1, wherein the first packet service session management request messageis at least one of a general packet radio service (GPRS) sessionmanagement (SM) message or an evolved packet system (EPS) sessionmanagement (ESM) message.
 3. The method of claim 2, wherein the firstnetwork element is at least one of a serving GPRS support node (SGSN) ora mobility management entity (MME).
 4. The method of claim 1 furthercomprising: setting an initial value of the retry timer of the UE basedon a first timer value, wherein, when UE receives a first messageincluding a timer value, the first timer value is the timer valueincluded in the first message.
 5. The method of claim 4 wherein thefirst message is the rejection message.
 6. The method of claim 4 furthercomprising: configuring a default timer value in the UE; wherein, whenthe UE does not receive a timer value in the first message, the firsttimer value is the default timer value configured in the UE.
 7. Themethod of claim 1 wherein the retry trigger event is at least one of theUE changing the public land mobile network (PLMN) the UE is connectedto, the UE changing a type of radio access technology (RAT) the UE isconnected to, the UE switching off, a subscriber identity module (SIM)of the UE changing, or a universal SIM (USIM) of the UE changing.
 8. Themethod of claim 7 further comprising: receiving, at the UE, an operationmode message; choosing, at the UE, between operating in a radio accesstechnology (RAT) dependent operation mode and operating in a RATindependent operation mode, based on the operation mode message.
 9. Themethod of claim 8, wherein the rejection message received at the UE isthe operation mode message.
 10. The method of claim 8 wherein, when theUE changes the type of RAT the UE is connected to, the UE does notinterpret the UE changing the type of RAT the UE is connected to as theretry triggering event, if the UE is operating in the RAT independentoperation mode, and the UE does interpret the UE changing the type ofRAT the UE is connected to as the retry triggering event, if the UE isoperating in the RAT dependent operation mode.
 11. A user equipment (UE)comprising: a processing unit including a processor, the UE beingprogrammed to perform, with the processor, operations including,sending, from the UE to a first network element, a first packet servicesession management request message indicating a request of a firstsession management service type for at least one of establishing a newpacket data session or modifying an existing packet data session, thefirst packet service session management request message being senttowards a first access point name (APN); receiving, at the UE, arejection message, the rejection message indicating the request for ofthe first session management service type has been rejected; andperforming a retry operation after receiving the rejection message, theretry operation including sending, from the UE, a second packet servicesession management request message of the first session managementservice type towards the first APN, the retry operation being preventedby the UE such that the retry operation is not performed by the UE untilafter at least one of, an expiration of a retry timer of the UE, ordetection, at the UE, of a retry trigger event.
 12. The UE of claim 11,wherein the UE is programmed such that first packet service sessionmanagement request message is at least one of a general packet radioservice (GPRS) session management (SM) message or an evolved packetsystem (EPS) session management (ESM) message.
 13. The UE of claim 12,wherein the UE is programmed such that first network element is at leastone of a serving GPRS support node (SGSN) and a mobility managemententity (MME).
 14. The UE of claim 11 wherein the operations the UE isprogrammed to perform further include: setting an initial value of theretry timer of the UE based on a first timer value; and wherein the UEis programmed such that, when the UE receives a first message includinga timer value, the first timer value is the timer value included in thefirst message.
 15. The UE of claim 14 wherein the UE is programmed suchthat the first message is the rejection message.
 16. The UE of claim 14wherein the operations the UE is programmed to perform further include:configuring a default timer value in the UE; and wherein the UE isprogrammed such that, when the UE does not receive a timer value in thefirst message, the first timer value is the default timer valueconfigured in the UE.
 17. The UE of claim 11 wherein the UE isprogrammed such that the retry trigger event is at least one of the UEchanging the public land mobile network (PLMN) the UE is connected to,the UE changing a type of radio access technology (RAT) the UE isconnected to, the UE switching off, a subscriber identity module (SIM)of the UE changing, or a universal SIM (USIM) of the UE changing. 18.The UE of claim 17 wherein the operations the UE is programmed toperform further include: receiving, at the UE, an operation modemessage; and choosing, at the UE, between operating in a radio accesstechnology (RAT) dependent operation mode and operating in a RATindependent operation mode, based on the operation mode message.
 19. TheUE of claim 18, wherein the UE is programmed such that the operationmode message is the rejection message received at the UE.
 20. The UE ofclaim 18 wherein the UE is programmed such that, when the UE changes thetype of RAT the UE is connected to, the UE does not interpret the UEchanging the type of RAT the UE is connected to as the retry triggeringevent, if the UE is operating in the RAT independent operation mode, andthe UE does interpret the UE changing the type of RAT the UE isconnected to as the retry triggering event, if the UE is operating inthe RAT dependent operation mode.